Closed
Bug 798609
Opened 12 years ago
Closed 12 years ago
disable android armv6 on mozilla-release
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
Attachments
(1 file)
3.35 KB,
patch
|
Callek
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
https://hg.mozilla.org/releases/mozilla-release/file/ddb22ac6c03b/mobile/android/config/mozconfigs/android-armv6/nightly is using beta branding where as armv7 is using release: https://hg.mozilla.org/releases/mozilla-release/file/ddb22ac6c03b/mobile/android/config/mozconfigs/android/nightly
Comment 1•12 years ago
|
||
do we do on-change builds of armv6 from mozilla-release? any new mozconfigs that need to be updated when we do beta->release merging can be added to here for future reference: https://wiki.mozilla.org/Release_Management/Merge_Documentation#Edit_mobile_mozconfigs but it also sure would be great to find a way to make sure this is auto-replaced some other way.
Comment 2•12 years ago
|
||
Also is this even relevant yet when we're not releasing ARMv6 builds until Firefox 17?
Assignee | ||
Comment 3•12 years ago
|
||
Erm. Our configs said that we were doing armv6 as of 16: https://github.com/mozilla/build-buildbot-configs/commit/7eed785ec6e11a551e57ac27c29f8e10901f01bf
Assignee | ||
Comment 4•12 years ago
|
||
Looks like we just need to update our mozconfig whitelists.
Component: General → Release Engineering: Automation (Release Automation)
Product: Fennec → mozilla.org
QA Contact: bhearsum
Summary: android armv6 branding is wrong on mozilla-release → update mozilla-release mozconfig whitelists
Version: Trunk → other
Assignee | ||
Comment 5•12 years ago
|
||
We got these errors in 16.0.1: 2012-10-10 14:14:13,814 : ERROR : found in mobile/android/config/mozconfigs/android-armv6/release but not in mobile/android/config/mozconfigs/android-armv6/nightly: ac_add_options --enable-updater 2012-10-10 14:14:13,815 : ERROR : found in mobile/android/config/mozconfigs/android-armv6/release but not in mobile/android/config/mozconfigs/android-armv6/nightly: ac_add_options --with-branding=mobile/android/branding/official 2012-10-10 14:14:13,815 : WARNING : ac_add_options --with-branding=mobile/android/branding/beta not in android-armv6 ['ac_add_options --enable-update-channel=nightly', 'ac_add_options --enable-update-channel=${MOZ_UPDATE_CHANNEL}', 'ac_add_options --enable-warnings-as-errors', 'ac_add_options --with-ccache=/usr/bin/ccache']! 2012-10-10 14:14:13,815 : ERROR : found in mobile/android/config/mozconfigs/android-armv6/nightly but not in mobile/android/config/mozconfigs/android-armv6/release: ac_add_options --with-branding=mobile/android/branding/beta 2012-10-10 14:14:15,754 : ERROR : Error verifying mozconfigs
Assignee | ||
Comment 6•12 years ago
|
||
After further investigation, it seems that we shouldn't be building armv6 at all, which may be why these mozconfig entries/whitelists didn't get looked at. We should just disable armv6 on mozilla-release until Firefox 17, when it's actually shipping.
Component: Release Engineering: Automation (Release Automation) → Release Engineering: Automation (General)
QA Contact: bhearsum → catlee
Summary: update mozilla-release mozconfig whitelists → disable android armv6 on mozilla-release
Assignee | ||
Comment 7•12 years ago
|
||
Attachment #670808 -
Flags: review?(bugspam.Callek)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bhearsum
Updated•12 years ago
|
Attachment #670808 -
Flags: review?(bugspam.Callek) → review+
Assignee | ||
Comment 8•12 years ago
|
||
Comment on attachment 670808 [details] [diff] [review] disable armv6 on mozilla-release Landed on default.
Attachment #670808 -
Flags: checked-in+
Comment 9•12 years ago
|
||
Live in production.
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•