Implement a fallback for bugbug optimization strategies
Categories
(Firefox Build System :: Task Configuration, task, P2)
Tracking
(firefox78 fixed)
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: ahal, Assigned: marco)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
If we want to use the bugbug service on autoland, we should have a fallback in the event the service goes down for an extended period of time. Currently the decision task would just fail and sheriffs would need to close the trees.
Instead we should fallback to using SETA or some other algorithm if there's a bugbug timeout. Having this fallback will allow us to get the optimizer on autoland sooner.
|
||
Comment 1•4 years ago
|
||
Can we have a daily stored artifact with information of what should be scheduled?
I would love to kill SETA :)
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 2•4 years ago
|
||
Pushed by mcastelluccio@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b99096a0996e Add an optional fallback for the bugbug optimizer and define a new strategy using it. r=ahal
|
Reporter | |
Comment 4•4 years ago
|
||
(In reply to Armen [:armenzg] from comment #1)
Can we have a daily stored artifact with information of what should be scheduled?
I would love to kill SETA :)
I think there's still some benefit in running the SETA shadow-scheduler as a benchmark even after it gets replaced. Don't worry, we can turn it off soon in a few months :p
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
Description
•