Repository navigation
Share one Flux allocation per child pipeline on Tioga and Tuolumne - #548
Merged
Merged
Conversation
Collaborator
Author
|
@lc-hubcast restart failed jobs |
|
I've retried any failed jobs in the pipeline! |
Collaborator
Author
|
@lc-hubcast restart pipeline |
|
I've started a new pipeline for you! |
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
1 participant
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.
Each commit currently submits about 49 standalone Flux jobs to the scheduler on each of Tioga and Tuolumne (about 98 total), mostly from the 39-job integration matrix. Running each child pipeline's jobs inside a single shared allocation cuts this to about 6 per machine (about 12 total) without dropping any tests. I received a message from LC folks asking if we could reduce the stress we place on the scheduler :)