ci: Remove self-hosted runner timeout jobs #40876
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Delan Azabani <dazabani@igalia.com>
jschwe
approved these changes
Nov 25, 2025
Member
|
Slightly off-topic:
Is it not 40 (I'm not sure where to check / see the number)? |
Member
Author
i think we had it upped from 20 to 60 in 2023, but i can't check anymore (it's in org settings). |
Member
|
sagudev
approved these changes
Nov 25, 2025
delan
added a commit
to servo/ci-runners
that referenced
this pull request
Dec 2, 2025
unfortunately neither the new global queueing feature (servo/servo#40852), nor dropping the runner-timeout jobs (servo/servo#40876), have improved self-hosted runner utilisation (a metric of server workload). that said, the self-hosted runner hit rate is 93%, so not too many jobs are missing out on self-hosted runners.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
the runner timeout jobs are a helpful safeguard against bugs (or github infra failures) that cause jobs to not get picked up by self-hosted runners, but all they do is wait two minutes and cancel the run, clogging up our github-hosted runner capacity (limited to 60).
this patch removes the timeout jobs, based on the expectation that our CI system is reliable enough to not need that automated safeguard.
if you have a build that gets stuck on “Waiting for a runner to pick up this job...”, it may be a bug or a github infra failure. you can cancel the build yourself, but please take a screenshot and report it first!
Testing: