Disable Android Nightly updates



5 years ago
3 months ago


(Reporter: armenzg, Assigned: nthomas)





5 years ago
15:37 AaronMT: so .... anyone else investigating the Nightly breakage? Too quiet
15:59 Guest: AaronMT: is it a problem with loading the strings in browser.properties?
16:00 Guest: I looked at the logcat from an attempted startup
16:02 Guest: nah, maybe not
16:02 Guest: life seems to go on after that
16:03 mfinkle: AaronMT, we should have disabled updates
16:04 mfinkle: :(
16:06 AaronMT: Guest: startup is fine, I see another error I'm about to file a bug for unrelated
16:08 AaronMT: SelectionHandler.js; getStringFromName
16:08 mfinkle: AaronMT, that is related to the locale issue
16:08 AaronMT: Yes I know, ought to clean them up to show the real problems
16:11 AaronMT: Guest: No chrome package registered for chrome://global/locale/intl.properties; No chrome package registered for chrome://browser/locale/browser.properties ?
16:14 mfinkle: right
16:14 Guest: AaronMT: yeah, that
16:14 mfinkle: open the APK, then open assets/omni.ja
16:14 mfinkle: then look in "chrome"
16:14 mfinkle: you should see a long list of locales
16:14 Guest: there's also a complaint about downloads.js trying to get alertDownloadsPause
16:14 mfinkle: i see none
16:14 mfinkle: there are no locales in the APK!
16:15 Guest: hooray!
16:15 mfinkle: rnewman, ^
16:16 mfinkle: armenzg, do we know if any changes landed for the locale repacks?
16:17 mfinkle: AaronMT, what's the main bug?
16:17 mfinkle: might as well dupe the rest to it
16:18 AaronMT: mine is bug 945723; b2g is bug 945750
16:18 firebot: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=945723 blo, --, ---, rnewman, NEW, JavaScript Error: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXULChromeRegist
16:18 firebot: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=945750 cri, P1, ---, gsvelto, ASSI, Desktop b2g fails to startup: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXUL
16:19 armenzg: mfinkle: not that I know of https://wiki.mozilla.org/ReleaseEngineering:Maintenance#Reconfigs_.2F_Deployments and http://hg.mozilla.org/build/mozharness/graph
16:20 mfinkle: armenzg, something happened that is stopping any locales, even en-US, from being added to the repack
16:20 armenzg: mfinkle: do you need us to disable the updates?
16:20 mfinkle: armenzg, is there a tbpl for the repacks?
16:20 mfinkle: armenzg, yes, we should disable updates
16:21 armenzg: mfinkle: I don't know the process - I thought it is all part of the nightly build
16:21 AaronMT: lots of build config changes in the pushlog
We "disabled" these by pointing at the last good update (20131202092621). When we're ready to re-point at the latest nightly, we need to point the rule in balrog back at Fennec-mozilla-central-nightly-latest.

Comment 2

5 years ago
Please assign to buildduty when ready to revert.

Many thanks Ben!

16:36 bhearsum: fennec nightly updates are pointing there now
16:36 bhearsum: eg, https://aus4.mozilla.org/update/4/Fennec/27.0a1/20130930093916/Android_arm-eabi-gcc3/en-US/nightly/4.2.2/default/default/27.0a1/update.xml
16:37 mfinkle: thanks
16:37 bhearsum: yw
16:38 bhearsum: once you know you have a working nightly just let us know and we'll repoint updates back to the latest
Assignee: nobody → mark.finkle
Last Resolved: 5 years ago
Resolution: --- → FIXED
The newest Nightly appears to work correctly and it has all expected locales in omni.ja.

Let's revert back to latest.
Assignee: mark.finkle → buildduty

Comment 4

5 years ago
Just waiting for the Android 2.2 build to complete first.
Resolution: FIXED → ---


5 years ago
Assignee: buildduty → nthomas

Comment 5

5 years ago
Pointed back to Fennec-mozilla-central-nightly-latest.

eg http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2013/12/2013-12-02-09-26-21-mozilla-central-android/fennec-28.0a1.multi.android-arm.apk for armv7.
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED


5 years ago
Depends on: 945968


3 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.