ArbPL fancy logs are back and standalone. no server.

Andrew Sutherland asutherland at asutherland.org
Mon Dec 2 21:44:14 UTC 2013


Just a note to say I just rebuilt the standalone logger recently so now 
it has some focus bugs fixed. 
https://bugzilla.mozilla.org/show_bug.cgi?id=944367 proposes removing or 
porting the extra features we added to Log4moz.jsm which is now 
available in-toolkit under a different name.  I'm not sure if active 
contributors know about the fancy structured logging, so I thought I'd 
point it out if you like it before it's gone.

Here's an example of it on a recent mozmill intermittent orange from 
Saturday:
https://clicky.visophyte.org/tools/arbpl-mozmill-standalone/?log=https://clicky.visophyte.org/examples/arbpl-mozmill/20131201/mozmill-fail.log

Unfortunately, it appears TBPL's "Download Raw Log" links for 
Thunderbird are inaccurate and the TBPL getParsedLog.php performs entity 
escaping that is potentially ambiguous on the log.  Does anyone know if 
there's an easy way to transform the build id and branch into an 
externally accessible log?  I skimmed the TBPL source for obvious raw 
options or how it got the logs, but it seems like the logs come from a 
database and there was no easily discoverable high level architectural 
explanation for TBPL.  I am happy to make the standalone logger a little 
more robust since auto-scraping right now is effectively broken.

Andrew

On 02/07/2012 07:54 PM, Andrew Sutherland wrote:
> Back in March of 2011 Thunderbird's mozmill tests gained exciting JSON 
> log output formats.  The announcement on tb-planning was here:
> https://mail.mozilla.org/pipermail/tb-planning/2011-March/000858.html
>
> The viewing mechanism for these was hosted on arbpl.visophyte.org.  
> ArbPL provided two things:
> 1) A TBPL-ish server that scraped tinderbox results in order to 
> provide build result summaries.  You can see what it looked like on 
> these blog posts: http://www.visophyte.org/blog/?p=745 
> http://www.visophyte.org/blog/?p=732
> 2) The ability to view the logs it scraped out of the tinderbox logs.  
> The logs look like you can see on this blog post: 
> http://www.visophyte.org/blog/?p=722
>
> The server went away because no one seemed to be using it and there 
> were some upkeep hassles.  Earlier this afternoon mconley asked about 
> whether there is a way to view those logs, and so #2 is now back.  If 
> people actually care about #1, we can probably bring that back too.
>
> If you want to see the logs for a tinderbox run, what you want to do 
> is browse to:
> http://clicky.visophyte.org/tools/arbpl-mozmill-standalone/?log=TINDERBOXLOG 
>
>
> But instead of TINDERBOXLOG, you would include a URL to an actual 
> tinderbox log.  The easiest way is simply to:
> 1) open a new tab
> 2) paste the following URL into that address bar:
> http://clicky.visophyte.org/tools/arbpl-mozmill-standalone/?log=
> 3) click on a "U" build in Thunderbird's TBPL instance at 
> http://build.mozillamessaging.com/tinderboxpushlog/
> 4) Right click on the "view full log" or "view brief log" links that 
> appear in the lower left hand corner of your browser.
> 5) Paste that URL onto the end of that URL from step #2.  You do not 
> need to perform any escaping of the question mark or anything; I made 
> the code assume you just pasted it like a lazy person.  If you do it 
> the right way, it will probably work, I haven't tested that.
>
> We can probably modify Thunderbird's TBPL fork to provide such a link 
> directly.  I am unclear on the status of the fork.
>
> Here is an example of one of our current failures with a pre-made URL 
> for the curious but who don't want to spend a lot of time making a URL:
>
> http://clicky.visophyte.org/tools/arbpl-mozmill-standalone/?log=http://tinderbox.mozilla.org/showlog.cgi?log=ThunderbirdTrunk/1328617905.1328618660.23575.gz 
>
>
> Andrew
>
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning




More information about the tb-planning mailing list