Closed
Bug 1128660
Opened 9 years ago
Closed 9 years ago
Temporarily disable Flame OTA until we respin with changeset for bug 950934
Categories
(Release Engineering :: Release Requests, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: pbylenga, Assigned: nthomas)
References
Details
(Keywords: regression, smoketest, Whiteboard: disabled and re-enabled after fix)
See bug 1128566 (smoketest/sanity blocker). OTA needs to be turned off until new builds with the patch from https://bugzilla.mozilla.org/show_bug.cgi?id=950934 are finished spinning.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → nthomas
Assignee | ||
Comment 1•9 years ago
|
||
Changed the rule for flame on nightly channel to be No-Update (was B2G-mozilla-central-kitkat-nightly-latest).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Flags: needinfo?(taz)
Reporter | ||
Comment 2•9 years ago
|
||
Can we re-enable the updates now that we have the build: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-kk/2015/02/2015-02-02-15-42-35/ Thank you!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 3•9 years ago
|
||
Verified B2G-mozilla-central-kitkat-nightly-latest contained the right build (http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/2015/02/2015-02-02-15-42-35-mozilla-central-flame-kk/b2g-flame-gecko-update.mar), and changed the rule back to that.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Summary: Disable Flame OTA until we respin with changeset for bug 950934 → Temporarily disable Flame OTA until we respin with changeset for bug 950934
Whiteboard: disabled and re-enabled after fix
Comment 5•9 years ago
|
||
Verified fixed. Flame OTA is working properly. Environmental Variables: Device: Flame 3.0 (319MB)(Full Flash) Build ID: 20150323010204 Gaia: 9b6f3024e4d0e62dd057231f4b14abe1782932ab Gecko: e730012260a4 Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 39.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•