[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-validation
Subject:    [Linaro-validation] tip build mmtest failures in lava
From:       michael.hudson () linaro ! org (Michael Hudson-Doyle)
Date:       2012-06-13 1:41:44
Message-ID: 87fwa0dm3r.fsf () canonical ! com
[Download RAW message or body]

Alexander Sack <asac at linaro.org> writes:

> On Tue, Jun 12, 2012 at 8:20 PM, Alexander Sack <asac at linaro.org> wrote:
> > On Tue, Jun 12, 2012 at 8:04 PM, Paul Larson <paul.larson at linaro.org> wrote:
> > > 
> > > On Tue, Jun 12, 2012 at 12:52 PM, Alexander Sack <asac at linaro.org> wrote:
> > > > 
> > > > On Tue, Jun 12, 2012 at 7:31 PM, Zach Pfeffer <zach.pfeffer at linaro.org>
> > > > wrote:
> > > > > On 12 June 2012 12:21, Alexander Sack <asac at linaro.org> wrote:
> > > > > > On Tue, Jun 12, 2012 at 7:10 PM, Zach Pfeffer <zach.pfeffer at \
> > > > > > linaro.org> wrote:
> > > > > > > On 12 June 2012 11:55, Alexander Sack <asac at linaro.org> wrote:
> > > > > > > > On Tue, Jun 12, 2012 at 6:54 PM, Zach Pfeffer
> > > > > > > > <zach.pfeffer at linaro.org> wrote:
> > > > > > > > > On 12 June 2012 09:02, Alexander Sack <asac at linaro.org> wrote:
> > > > > > > > > > Hi,
> > > > > > > > > > 
> > > > > > > > > > looking at origen and snowball lava results from our tip builds I
> > > > > > > > > > realized that mmtest's are failing:
> > > > > > > > > > 
> > > > > > > > > > origen:
> > > > > > > > > > https://android-build.linaro.org/builds/~linaro-android/origen-ics-gcc47-samsunglt-stable-blob/#build=51
> > > > > > > > > >                 
> > > > > > > > > > ->
> > > > > > > > > > http://validation.linaro.org/lava-server/dashboard/streams/private \
> > > > > > > > > > /team/linaro/android-daily/bundles/07507b2bf67f49bc104878de3a9f03d5eb4ee99f/9ffd7ee6-f64e-4d26-ab41-373ec932dec8/
> > > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > I get a 404 error for this one ^^^^^^^^^^^^^
> > > > > > > > 
> > > > > > > > 
> > > > > > > > you have to be logged into validation.linaro.org to see any raw
> > > > > > > > results nowadays. try that.
> > > > > > > 
> > > > > > > That worked better. How can I download the log? Every time I try and
> > > > > > > save it its giving me a download.html file?
> > > > > > > 
> > > > > > 
> > > > > > Good question. Only thing I know is how to open the "inline" view ...
> > > > > > I guess there is a secret link to download attachment, but yes, I also
> > > > > > have a hard time spotting the download link for it (e.g. stdout.log)
> > > > > > > /
> > > > > 
> > > > > Yeah, the inline view just errors out.
> > > > 
> > > > its a timeout... if you reload it might work better :)
> > > > 
> > > Yeah, it comes up just fine for me. I seem to recall that if attachments
> > > are too huge, uwsgi will even timeout. Adding a download link instead of
> > > just the inline viewer would be good. If you still can't get to it in the
> > > inline viewer, you can also see it in the context of the full log here:
> > > http://validation.linaro.org/lava-server/scheduler/job/22004/log_file
> > > 
> > 
> > +1 on the direct download link.
> > 
> > How about we kill the whole inline viewer tab and just grow the
> > attachment information view with a "direct download" link?
> > 
> > Basically just have
> > 
> > + http://validation.linaro.org/lava-server/dashboard/streams/private/team/linaro/a \
> > ndroid-daily/bundles/07507b2bf67f49bc104878de3a9f03d5eb4ee99f/9ffd7ee6-f64e-4d26-ab41-373ec932dec8/attachments/79745/
> >  
> > without the tabs and with a direct download link next to the other meta info.
> 
> 
> Checking dashboard_app/templates/dashboard_app/attachment_detail.html
> in latest lp:lava-dashboard I noticed that we display
> "attachment.public_url" if that field is set for an attachment.
> However, this attachment seems to not have a public_url. Anybody knows
> why that is and what the public_url field was intended to be used for?

It's used for things like the results of jobs in Jenkins, where it can
point to e.g. the build log in jenkins.

Cheers,
mwh


[prev in list] [next in list] [prev in thread] [next in thread]