Android Nightly builds broken since August 31st

RESOLVED FIXED

Status

()

Firefox for Android
Build Config & IDE Support
RESOLVED FIXED
11 months ago
11 months ago

People

(Reporter: njn, Assigned: dbaron)

Tracking

({regression})

Trunk
regression
Points:
---

Firefox Tracking Flags

(firefox-esr52 unaffected, firefox55 unaffected, firefox56 unaffected, firefox57 fixed)

Details

(URL)

(Reporter)

Description

11 months ago
According to https://dbaron.org/mozilla/crashes-by-build, Android Nightly builds last shipped on August 30th.

(Bug 1366729 was the last time this happened, in case that's helpful.)

I looked at
https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=nightly&fromchange=13d241d08912be31884f9d0d0e805b25343d6c0a
but I don't know enough about Nightly build generation to understand how the various failures we see there (e.g. "Ugs") might impact Nightly build generation. I did notice that 

catlee, gps: any idea what might be wrong? I wonder if this is related to bug 1349227.
Flags: needinfo?(gps)
Flags: needinfo?(catlee)
(Reporter)

Comment 1

11 months ago
In case it's relevant: Linux builds also appear to have been missed for September 1, but they are back on September 2 and 3.
(Reporter)

Comment 2

11 months ago
It's also possible that the builds are occurring but https://dbaron.org/mozilla/crashes-by-build is not picking them up. dbaron, can you tell if that's the case?
Flags: needinfo?(dbaron)
Fixed in:
https://hg.mozilla.org/users/dbaron_mozilla.com/nightly-topcrash-generator/rev/d3f2c759203f
or if you prefer git:
https://github.com/dbaron/nightly-topcrash-generator/commit/e94ccc9d4f67d89d5e95de82255515df8bc87b00
Assignee: nobody → dbaron
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Flags: needinfo?(dbaron)
Resolution: --- → FIXED
Blocks: 1384482
Flags: needinfo?(gps)
Flags: needinfo?(catlee)
status-firefox57: affected → fixed
status-firefox55: --- → unaffected
status-firefox56: --- → unaffected
status-firefox-esr52: --- → unaffected
You need to log in before you can comment on or make changes to this bug.