I often find that I cannot build Firefox using the default "hg pull" command. To determine the cause of a build failure, it is helpful to pull the latest source code that has passed the Mozilla automatic tests. That turns out to be rather involved, so here are some notes that Dave Townsend and Ehsan posted to mozilla.dev.builds newsgroup.
Dave Townsend wrote:
On 24/04/2009 17:19, Dave Townsend wrote:Well you could just look at tinderbox to see how green the tree is, though often there are known random failures in play so it can be tricky to identify exactly how good the build is. But in general if it isn't burning it should be mostly usable.
Ok thanks, I now remember stopping after puzzling over 'how green" and lots of boxes with puzzling labels and contents. I guess Win 5.2 == Win XP?
Windows XP is Win 5.1. Win 5.2 is Windows 2003. But I don't think that it should matter for your purposes.
So I want to look in the column "WINNT 5.2 mozilla-central unit test"?
If all you want to do is to make sure that the build works, you should look under the "WINNT 5.2 mozilla-central build" column. Here is how a successful entry looks like: L "rev:531f60d6cf88" With L meaning "log", and "rev:" meaning the revision of course.
There I see some yellow and green boxes, one of them says:
Yellow boxes are tasks currently running, you may ignore them for the purpose of checking out the tree status.
L periodic clobber "rev:abc59dbb6e46" RLk:0B Lk:110KB MH:14.8MB A:380604
This actually looks like the entries under the leak test machine. The meaning of each item appears as a tooltip when you hover its name.
I know this info is helpful, but how so? If the box is green I can put the rev: number into an hg command?
If all you want to do is to make sure that your revision compiles fine, then you should be safe if the build box is green. If you want to make sure that it actually works correctly you should see if the unit test box is green as well, but as Dave mentioned this can be tricky because of intermittent oranges. If for example you see that revision 531f60d6cf88 is good enough, you should do the following locally and start a build: hg pull hg up 531f60d6cf88 HTH, -- Ehsan