Closed Bug 1003634 Opened 11 years ago Closed 10 years ago

Touch CLOBBER on branches being uplifted

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: mozilla)

References

Details

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.
Were these after my push from aurora, or after your push from beta?
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.
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?
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
Blocks: 1011794, 1011796
Assignee: nobody → aki
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.
Landed in bug 1011796.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.