Releases/Firefox 17.0b6/BuildNotes: Difference between revisions

Releases/Firefox 17.0b6/BuildNotes (view source)

Revision as of 14:02, 14 November 2012

3,202 bytes added , 14 November 2012

no edit summary

Bhearsum

canmove, Confirmed users

6,441

edits

@@ Line 31: / Line 31: @@
 Aki told me that the signing scripts are safely rerunnable, so I reran the same commands after the repacks had finished.
+=== Fix schedulers that didn't fire correctly ===
+On Wednesday morning, I noticed that updates still weren't ready. I looked through my e-mail and confirmed that I had received all of the "all $platfrom builds now available" mails. Then I went poking around the database. I found that two of the schedulers with "release-mozilla-beta-linux64_build" as an upstream hadn't been properly updated when it had completed:
+ | release-mozilla-beta-firefox_deliverables_ready   | {"remainingBuilders": ["release-mozilla-beta-linux64_build"], "upstreamBuilders": ["release-mozilla-beta-firefox_source", "release-mozilla-beta-linux_build", "release-mozilla-beta-linux_repack_complete", "release-mozilla-beta-linux64_build", "release-mozilla-beta-linux64_repack_complete", "release-mozilla-beta-win32_build", "release-mozilla-beta-win32_repack_complete", "release-mozilla-beta-macosx64_build", "release-mozilla-beta-macosx64_repack_complete"], "lastReset": 1352817804.972043, "lastCheck": 1352843283}              |
+ | release-mozilla-beta-firefox_signing_done | {"remainingBuilders": ["release-mozilla-beta-linux64_build"], "upstreamBuilders": ["release-mozilla-beta-linux_build", "release-mozilla-beta-linux_repack_complete", "release-mozilla-beta-linux64_build", "release-mozilla-beta-linux64_repack_complete", "release-mozilla-beta-win32_build", "release-mozilla-beta-win32_repack_complete", "release-mozilla-beta-macosx64_build", "release-mozilla-beta-macosx64_repack_complete"], "lastReset": 1352817804.9652419, "lastCheck": 1352843283} |
+However, the "release-mozilla-beta-linux64_repack" scheduler worked fine.
+ | release-mozilla-beta-linux64_repack             | {"remainingBuilders": ["release-mozilla-beta-linux64_build", "release-mozilla-beta-firefox_tag_l10n"], "upstreamBuilders": ["release-mozilla-beta-linux64_build", "release-mozilla-beta-firefox_tag_l10n"], "lastCheck": 1335386373}
+This is very confusing, because these schedulers would've been updated right at the same time after the linux64 build completed.
+To fix things up, manually altered the state of the broken schedulers:
+ update schedulers set state='{"remainingBuilders": [], "upstreamBuilders": ["release-mozilla-beta-linux_build", "release-mozilla-beta-linux_repack_complete", "release-mozilla-beta-linux64_build", "release-mozilla-beta-linux64_repack_complete", "release-mozilla-beta-win32_build", "release-mozilla-beta-win32_repack_complete", "release-mozilla-beta-macosx64_build", "release-mozilla-beta-macosx64_repack_complete"], "lastReset": 1352817804.9652419, "lastCheck": 1352843283}' where name='release-mozilla-beta-firefox_signing_done';
+ update schedulers set state='{"remainingBuilders": [], "upstreamBuilders": ["release-mozilla-beta-firefox_source", "release-mozilla-beta-linux_build", "release-mozilla-beta-linux_repack_complete", "release-mozilla-beta-linux64_build", "release-mozilla-beta-linux64_repack_complete", "release-mozilla-beta-win32_build", "release-mozilla-beta-win32_repack_complete", "release-mozilla-beta-macosx64_build", "release-mozilla-beta-macosx64_repack_complete"], "lastReset": 1352817804.972043, "lastCheck": 1352843283}' where name='release-mozilla-beta-firefox_deliverables_ready';