Closed Bug 1623094 Opened 5 years ago Closed 5 years ago

Stop using backoff_factor in the bugbug optimizer

Categories

(Firefox Build System :: Task Configuration, task, P3)

task

Tracking

(firefox76 fixed)

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: ahal, Assigned: ahal)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

I implemented a retry with backoff factor for the bugbug scheduler:
https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/optimize/bugbug.py#31

But in this case it makes sense to poll on a regular interval instead. The backoff factor approach assumes that the service is having issues that have a high probability of being fixed right away. Whereas in this case a status of 202 just means computation hasn't finished yet, and it's nearly as likely that it finishes in 2 seconds as it is in 1 second.

Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/93891e8ceb51 [taskgraph] Use regular retry interval when querying bugbug service, r=marco https://hg.mozilla.org/integration/autoland/rev/62a22274ff2c [ci] Enable debug logging for shadow-scheduler tasks, r=marco
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: