Address Documentation Issue #57: Include clarification on selecting multiple node selection parameters in USAGE.md #59
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.
Summary
USAGE.md mentions how tests can be configured using a combination of parameters. The host, job, and nodelabel parameters all involve node selection. To clarify behavior when multiple node selection parameters are used together, I mentioned that Autopilot runs the tests on nodes that match any of the specified parameters (set union rather than set intersection).
I specifically added the following sentences under the parameters list in USAGE.md: Note that if multiple node selection parameters (
host
,job
,nodelabel
) are provided together, Autopilot will run tests on nodes that match any of the specified parameters (set union). For example, the following command will run thepciebw
test on all nodes that either have the labellabel1
OR are running the jobjobKey=job2
because bothnodelabel
andjob
parameters are provided in the input:curl "http://<route-name>/status?check=pciebw&nodelabel=label1&job=default:jobKey=job2"
GitHub Issue
closes #57 - [Documentation] Clarification on node selection parameters in USAGE.md