Summary: tracking bug for build and release of Firefox 16.0b1 → tracking bug for build and release of Firefox 17.0b1
Created attachment 669556 [details] [diff] [review] release config
Created attachment 669590 [details] [diff] [review] release config + l10n changesets
Attachment #669590 - Flags: review?(kmoir) → review?(bhearsum)
Attachment #669590 - Flags: review?(bhearsum) → review+
Comment on attachment 669590 [details] [diff] [review] release config + l10n changesets Landed in https://hg.mozilla.org/build/buildbot-configs/rev/3c30da2c77da
Attachment #669590 - Flags: checked-in+
Current status: Mac: build ok, repacks failed Linux32: build ok, repacks failed Linux64: build ok, repacks failed Win32: build ok, repacks in progress Android: failed compile Android-armv6: failed compile
The repacks I referred to above are the 'l10n repacks' which generate localized builds. Without those, all we have are en_US builds. The win32 and Mac builds on ftp.m.o are usable for now. Linux32/64 build logs need more investigation for me to say to go ahead and test them, but you may if you wish. Android compiles are failing - something I need to detangle with RelEng tomorrow morning (we now depend on a newer android SDK which is not present on our linux-ix machines). The win32 l10n repacks also ended up failing like on the other platforms.
Already posted this on r-d email but for completeness I'm cross-posting here. QA is moving ahead with testing the en-US Desktop builds tonight. We'd rather accept the risk of a respin than to lose a full night of testing.
FWIW, our Mozmill automation encountered no failures on any platform with the en-US builds: http://mozmill-ci.blargon7.com/#/functional/reports?branch=17.0&platform=All&from=2012-10-09&to=2012-10-10
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.