Closed
Bug 1488686
Opened 6 years ago
Closed 6 years ago
52.9.0esr -> 60.2.0esr: wrong bouncer entries found by final-verify => "firefox-60.2.0esr-complete-bz2" doesn't exist
Categories
(Release Engineering :: Release Automation: Uploading, enhancement)
Release Engineering
Release Automation: Uploading
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1488518
People
(Reporter: jlorenzo, Unassigned)
References
Details
The final-verify job kept failing with [1], because the bouncer product "firefox-60.2.0esr-complete-bz2" wasn't created by automation. I manually added it. This led me to another issue: "firefox-60.2.0esr-complete" was pointing to the BZ2 updates instead of the LZMA ones. I fixed it manually too. Tom found it's an in-tree bug caused by [2]. We might be okay to not fix this, if we keep 60.2.0esr as a watershed for bz2 updates. If not, we should revisit [2]. [1] https://tools.taskcluster.net/groups/SkDMIM1HQMiDIPfzsl7qvA/tasks/FFiFlcEmR4-K3QgXGIWZLw/runs/4/logs/public%2Flogs%2Flive_backing.log#L5890 [2] https://searchfox.org/mozilla-central/rev/5a18fb5aeeec99f1ca1c36a697082c221189a3b9/taskcluster/taskgraph/transforms/bouncer_submission.py#242
|
Reporter | |
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
| Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•