DAOS-17209 test: Handle non-persistent PMEM naming (#16027) #16042
Conversation
This file contains 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
To avoid generating a server storage configuration in CI testing that uses ram instead of PMEM when PMEM exists on all the nodes in the cluster but it is located on different NUMA nodes, ignore the NUMA association. Skip-unit-tests: true Skip-fault-injection-test: true Test-tag: test_setup Signed-off-by: Phil Henderson <phillip.henderson@hpe.com>
|
Ticket title is 'Functional tests not run with PMEM due to pmem[0,1] block devices configured on different NUMA nodes' |
daltonbohning
approved these changes
Mar 5, 2025
phender
added
clean-cherry-pick
JohnMalmberg
approved these changes
Mar 5, 2025
|
Force landing required as only a single test was needed in a Functional HW Medium and Large stage to verify the change. |
This was referenced Mar 10, 2025
Closed
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.
To avoid generating a server storage configuration in CI testing that uses ram instead of PMEM when PMEM exists on all the nodes in the cluster but it is located on different NUMA nodes, ignore the NUMA association.
Skip-unit-tests: true
Skip-fault-injection-test: true
Test-tag: test_setup
Steps for the author:
After all prior steps are complete: