Closed Bug 1432335 Opened 2 years ago Closed 2 years ago

Firefox 58 Release Uptake Monitoring failed, due to missing bz2 mar's

Categories

(Release Engineering :: Release Automation: Other, enhancement)

enhancement
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: bhearsum)

Details

Attachments

(1 file)

The code for this is in-tree (mozharness) and:

$ taskcluster group list AtQ39aLrRPae7xT5-RjPPA --format-string "{{ .Task.Metadata.Name }} {{ .Status.TaskID }} {{ .Task.Dependencies }}" --all | grep PKlF2T-ST2un27ADYDvM7g

mozilla-release release final verification LbkT6n_dQz-U6t17--2eqg [PKlF2T-ST2un27ADYDvM7g]
firefox mozilla-release uptake monitoring PKlF2T-ST2un27ADYDvM7g [WAouX0kUSeinFF2HPPP2yQ]
firefox email release-drivers release-cdntest WYYgoNC3Rk6e7Orru6d-ng [PKlF2T-ST2un27ADYDvM7g]

Means we block e-mailing release drivers and block final verify on this task... I'm going to trigger final-verify using the 'hack' of cancel + rerun (so it ignores deps)
Looks like we need to remove the bz2 entries from https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/releases/bouncer_firefox_release.py (and backport to mozilla-beta).
It looks like we would've hit this issue for 52.6.0 had we not hit deadline-exceeded (https://tools.taskcluster.net/groups/EP95aXu5SCqdudWWKY50EQ/tasks/d2cNqkSXRiSU00HUvpEutQ/details).
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Attachment #8946256 - Flags: review?(bugspam.Callek)
Attachment #8946256 - Flags: review?(bugspam.Callek) → review+
Pushed by bhearsum@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/4949b8ab4d34
remove bz2 remnants from release & esr. r=callek
Comment on attachment 8946256 [details] [diff] [review]
remove bz2 remnants from release & esr

I pushed this to beta & release as well. Turns out esr52 doesn't have a bz2 block, so nothing is needed there.
Attachment #8946256 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.