Closed
Bug 1878065
Opened 5 months ago
Closed 5 months ago
Try selections getting optimized
Categories
(Developer Infrastructure :: Try, defect)
Developer Infrastructure
Try
Tracking
(firefox-esr115 unaffected, firefox122 unaffected, firefox123 unaffected, firefox124 fixed)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox122 | --- | unaffected |
| firefox123 | --- | unaffected |
| firefox124 | --- | fixed |
People
(Reporter: ahal, Assigned: ahal)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
As result of a regression from bug 1608026, tasks selected in a try push are being optimized away.
|
||
Comment 1•5 months ago
|
||
Set release status flags based on info from the regressing bug 1608026
status-firefox122:
--- → unaffected
status-firefox123:
--- → unaffected
status-firefox124:
--- → affected
status-firefox-esr115:
--- → unaffected
|
Assignee | |
Comment 2•5 months ago
|
||
Prior to bug 1878065, we were using whether the 'try_task_config.json' was v1
or v2 as the indication to whether or not 'optimize_target_tasks' should be
True or False. But now that everything is using v2, this can no longer be
relied upon.
Instead, set 'optimized_target_tasks' on the tryselect side as the various
selectors can override the default as needed.
Pushed by sstanca@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/366005a91eda [tryselect] Explicitly set 'optimize_target_tasks' in try_task_config.json, r?#releng-reviewers!
|
||
Comment 4•5 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•