feat: randomize runner selection#3722
Merged
fiftin merged 3 commits intosemaphoreui:developfrom Mar 31, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates remote-runner task scheduling to reduce repeated selection of the same runner by randomizing the order in which eligible runners are considered, while still preferring project runners over global runners.
Changes:
- Added a
shuffleRunnershelper to randomize runner ordering. - Shuffled project and global runner lists before concatenating them for selection.
Work on a copy so that if randomness fails, we can safely return the original order. Co-authored-by: Copilot <[email protected]>
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
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.
Hello!
Just ran into same issue as mentioned here:
#1519 (comment)
For me, tasks also kept scheduling on the same runner
Seems that issue is fixed by adding 2 shuffle calls, still keeping "project" runners preferred over "global" ones
To verify that tasks are distributed randomly, I've built and ran docker image locally:
semaphoreui/semaphore:v2.17.28agrrh/semaphoreui:random-runner-selection(First contribution here, please, let me know if I missed something)