actions: allow runner-select to generate runner indices #93
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
This was referenced Dec 4, 2025
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.
this patch builds on #92, adding some supporting features to runner-select that will allow us to eliminate the “generate chunks” job in our WPT workflow:
github-hosted-runner-count(default 1) and the new outputselected-runner-countallow the action to switch between two different runner counts for GitHub-hosted and self-hosted casesfirst-runner-index(default 0) and the new outputselected-runner-indicesallow the action to generate a JSON array of runner indices or chunk ids as required by the WPT runnerif we landed #92 only, the WPT workflow would still need to run a job to generate chunk ids between runner-select and the workload (it would
needsrunner-select, and the workload wouldneedsboth). this is dangerous because that job may get delayed due to lack of GitHub-hosted runner capacity. if it gets delayed, the reservation may time out, and the workflow run will get stuck waiting forever for runners that will never come back.test runs: #21 (comment)