9.43 KB, application/zip
26.08 KB, application/zip
1.55 KB, patch
|Details | Diff | Splinter Review|
Created attachment 8444414 [details] Zipped Logcat output of failed update attempt 1. Device: Flame. 2. Current Base build. 3. Flashed newest shallow master (Gaia + Gecko) Friday morning EDT using the QA auto flash tool. 4. Today, attempted to update via the built-in software update under Settings/Device Information/Check for Updates. 5. I was offered a system update. Went to notifications and then opened the update dialog and chose to download. 6. Download completed, I got a message saying "Uncompressing, this can take a few minutes". 7. After 2 to 3 minutes, got a message saying "There was an error while downloading", and the notification went back to "! Update available". 8. Started logcat and started recording output. 9. Opened the Update dialog again and hit Download. 10. Instead of downloading again, it went straight to uncompressing, and failed again. Log is attached. I stopped it after the error message came and went that said "There was an error while downloading the update". Zipped output attached.
Sorry, forgot to mention, the Shallow build was an eng build, not a usr one.
Adding qawanted to see if someone else can confirm.
We don't (or shouldn't, at least) be providing updates for Eng builds. Are you being offered one?
It would also be helpful to have logcat output during the update attempt. Particularly any "AUS:SVC" and "GeckoUpdater" lines.
Hi Ben, yes I am being offered updates for eng builds. And the attached log output is from such an attempt, or even two I believe.
Comment on attachment 8444414 [details] Zipped Logcat output of failed update attempt I think this has an already cached MAR...can you try again, maybe after reflashing? I'm expecting to see a line that include "https://aus4.mozilla.org" in it.
Created attachment 8452284 [details] Update download and uncompressing, but too low battery This shows the download and uncompressing of an update, including the Check for Update process. However, since my battery was too low, I didn't actually have a chance to go through with the actual update try, but this should give you the info you need.
Thanks Marco. Indeed, the eng builds seem to report the same data as the user builds to AUS. What's worse, in your second log is actually _did_ apply the update. At your next boot you're going to be on either a full user build or a frankenbuild combination of eng+user. We'll need to somehow change something about the eng builds to make sure they don't get offered updates.
Assignee: nobody → bhearsum
Created attachment 8452298 [details] [diff] [review] try to set eng channel differently It looks like this is the standard way of dealing with things that are set in the gecko config, but should actually be set to something else for some variants (ie, VARIANT in eng builds).
Attachment #8452298 - Flags: review?(aki)
Summary: Update attempts fail for current FF OS shallow Master builds → FxOS eng builds shouldn't receive updates
Comment on attachment 8452298 [details] [diff] [review] try to set eng channel differently I landed this on default+production. I'll have a look at the nightly builds tomorrow to see if it worked.
Component: General → General Automation
Product: Firefox OS → Release Engineering
QA Contact: catlee
Attachment #8452298 - Flags: checked-in+
The latest eng nightly has "default" as a channel. Shouldn't be a problem from now on.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.