ci: Use new queue API for self-hosted runners #40852
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this patch enables CI jobs to queue for self-hosted runners by bumping our actions to servo/ci-runners#69, and bumping our runner-select and runner-timeout jobs to ubuntu-24.04 (for better retry support in curl).
this should further speed up our builds by allowing more jobs to run on self-hosted runners: if a job would take 5x as long on github-hosted runners, then we can wait up to 80% of that time for a self-hosted runner and still win.
for now, though, jobs will queue for self-hosted runners for up to one hour (note that you won’t have to wait if the servers are down). if your request for a self-hosted runner can’t be satisfied immediately, it will look like this:
to check where you are in the queue, go to https://ci0.servo.org/queue/ (it’s currently very rudimentary):
Testing: