Adds a multi_node_queue_name
ci config option
#504
Merged
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.
If specified, this option allows multi-node tests to run using a different queue than the one in
queue_name
. The wisdom of this is that on certain systems it makes sense to use more restrictive but less expensive queues by default, and only use more expensive, multi-node queues when strictly needed. In a sense, this could be hacked usingcustom_attributes
and test filters, which some deployments do, but it is awkward and difficult to set up in a way that predicts all future multi-node tests.When merged, the new
ci_runner.py
will automatically be used by all deployed tests. It was modified to not pass configoptions that are not set, and all such options should have defaults in the
conftest.py
arg parser, both old and new.This addition will affect tests that are currently deployed as follows (new and old refer to post and pre merging this PR):