Closed
Bug 1808245
Opened 1 year ago
Closed 1 year ago
default to stopping fast-forward processing when target branch-head is reached
Categories
(Core :: WebRTC, task, P2)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
110 Branch
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: mjf, Assigned: mjf)
References
Details
Attachments
(2 files)
Currently, unless MOZ_STOP_AFTER_COMMIT
has been set, loop-ff.sh
will attempt to advance indefinitely. We should really default to stopping at the target branch-head (set in MOZ_GIT_RELEASE_BRANCH) to avoid unnecessary processing errors when loop-ff.sh
hits then end of the branch-head.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Summary: default to stopping fast-forward processing with target branch-head → default to stopping fast-forward processing when target branch-head is reached
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
Depends on D165838
Updated•1 year ago
|
Attachment #9310438 -
Attachment description: Bug 1808245 - pt1 - by default, stop fast-forward processing when target branch-head is reached. r=ng! → Bug 1808245 - pt1 - by default, stop fast-forward processing when target branch-head is reached. r=dbaker!
Updated•1 year ago
|
Attachment #9310439 -
Attachment description: Bug 1808245 - pt2 - detect end of processing and quit. r?ng! → Bug 1808245 - pt2 - detect end of processing and quit. r?dbaker!
Pushed by mfroman@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f5ea9c658d0b pt1 - by default, stop fast-forward processing when target branch-head is reached. r=dbaker DONTBUILD https://hg.mozilla.org/integration/autoland/rev/83ceaa30219b pt2 - detect end of processing and quit. r=dbaker DONTBUILD
Comment 4•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f5ea9c658d0b
https://hg.mozilla.org/mozilla-central/rev/83ceaa30219b
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•