Repository navigation
Allow pinning the Permian daily run to a specific runner - #1765
Merged
Merged
Conversation
The daily run was hardwired to the "kstest" runner pool, so there was no way to send it at one particular machine. That makes it awkward to try out a new dedicated runner: until it is trusted enough to join the pool, nothing can be routed to it. Add a workflow_dispatch input carrying a runner label, which replaces "kstest" rather than being added to it, so the target runner does not have to be in the "kstest" pool at all. "self-hosted" is always kept. The scheduled run supplies no inputs and so keeps using "kstest", leaving the daily results coming from the trusted pool. Assisted-by: Claude Opus 5
KKoukiou
approved these changes
Sep 25, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 daily run was hardwired to the "kstest" runner pool, so there was no way to send it at one particular machine. That makes it awkward to try out a new dedicated runner: until it is trusted enough to join the pool, nothing can be routed to it.
Add a workflow_dispatch input carrying a runner label, which replaces "kstest" rather than being added to it, so the target runner does not have to be in the "kstest" pool at all. "self-hosted" is always kept. The scheduled run supplies no inputs and so keeps using "kstest", leaving the daily results coming from the trusted pool.
Assisted-by: Claude Opus 5
Note: required to help testing the migration to new runners and I tested it on my fork