Touch CLOBBER on branches being uplifted

RESOLVED FIXED

Status

Release Engineering
General Automation
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: RyanVM, Assigned: aki)

Tracking

(Blocks: 2 bugs)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
We've hit oranges on b2g30 post-uplift that we have some reason to believe are needs-clobber in nature. I've manually clobbered the tree, but I think it would be more reliable to add an ffxbld CLOBBER touch step instead.
(Assignee)

Comment 1

3 years ago
Were these after my push from aurora, or after your push from beta?
(Reporter)

Comment 2

3 years ago
My beta push, but given the rate of failure so far (1 b2g emulator run yesterday and 1 win debug run today), I can't say for sure what the meaning of it is.
(Assignee)

Comment 3

3 years ago
The merge script doesn't really have much to do with either; it's for release/beta/aurora. I was done manually pushing to b2g30 after the aurora push.  Thinking this is a wontfix; what do you think?
(Reporter)

Comment 4

3 years ago
I still think this is something we should do on the other release branches. Just because this happened most recently on b2g30 doesn't mean it can't happen elsewhere as well. FWIW, doing a manual clobber was part of the RelMan merge day documentation:
https://wiki.mozilla.org/Release_Management/Merge_Documentation
(Assignee)

Updated

3 years ago
Blocks: 1011794, 1011796
(Assignee)

Updated

3 years ago
Assignee: nobody → aki
(Assignee)

Comment 5

3 years ago
Added CLOBBER to the new gecko_migration.py script:
https://github.com/escapewindow/mozharness/commit/e3581b46de9b47b2b21633626936cc69f648522f

I'm getting close to review ready.  I'll probably use bug 1011796 for this.
(Assignee)

Comment 6

3 years ago
Landed in bug 1011796.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.