On http://l10n.mozilla.org/~axel/nightlies/?date=2010-11-19&buildbot=true, there's a very sparse, not sure if those builds weren't triggered, or if the builds json that that display is based on is not picking up all masters.
Can you give a specific example of one that wasn't built or was built but not reported? I don't know what I should be looking for on that page.
http://l10n.mozilla.org/~axel/nightlies/?date=2010-11-17&buildbot=true is the common pattern. The 18th looks sparse, too.
Please give me a locale to go track down.
ast, linux, mozilla-central. Nothing specific about branch, platform, locale in that example.
So ast got ran on mozilla-central Linux both on the 18th and 19th. Today it ran on buildbot-master2 and completed successfully at 03:36:08. So statusdb isn't getting updated somehow?
It's in statusdb... Which json files are you scraping?
It's in http://build.mozilla.org/builds/builds-2010-11-19.js.gz as far as I can tell.
Not sure how I came up with that combo, 'be' 'mozilla-central' 'linux' is one, and all of mozilla-central osx, apparently
.... and I'm scraping the builds-2010-11-20.js.gz file, fwiw.
(In reply to comment #9) > .... and I'm scraping the builds-2010-11-20.js.gz file, fwiw. data from the future!!!
'be' 'mozilla-central' 'linux' finished at 03:37:54 on production-master03...and updates into statusdb are busted on production-master03. production-master01 was also busted. The other masters seem unaffected.
Fixed up pm01/pm03, and imported all the old data, and re-generated builds-2010-11-18.js.gz. (2010-11-19.js.gz will get refreshed automatically).
Oy, much better, thanks. Can you regenerate the 17th, too? Updated the processed data for 18th and 19th.
(In reply to comment #13) > Oy, much better, thanks. > > Can you regenerate the 17th, too? > > Updated the processed data for 18th and 19th. Done!