ArbPL fancy logs are back and standalone. no server.

Joshua Cranmer 🐧 Pidgeot18 at gmail.com
Mon Dec 2 22:41:25 UTC 2013


On 12/2/2013 3:44 PM, Andrew Sutherland wrote:
> 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.

I knew about it, I just figured you'd shut down ArbPL long ago.
>
> 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.

Looking at the network traffic for TBPL reveals that the JSON request 
https://tbpl.mozilla.org/php/getRevisionBuilds.php?branch=<branch>&rev=<revision> 
returns an array of
{log: <URL to the build log on FTP>, _id: <build id>}. This requires you 
to know the revision number as well, though.


-- 
Joshua Cranmer
Thunderbird and DXR developer
Source code archæologist




More information about the tb-planning mailing list