-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge release/2.6 into google/2.6 #16076
Merged
Merged
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
Collaborator
juszhan1
commented
Mar 11, 2025
- DAOS-17209 test: Handle non-persistent PMEM naming (DAOS-17209 test: Handle non-persistent PMEM naming #16027) (DAOS-17209 test: Handle non-persistent PMEM naming (#16027) #16042)
- DAOS-17094 test: auto storage config for daos_server_restart (DAOS-17094 test: auto storage config for daos_server_restart #16050)
- DAOS-623 ci: Simplify the pull request template (DAOS-623 ci: Simplify the pull request template #15969) (DAOS-623 ci: Simplify the pull request template (#15969) #16020)
- DAOS-17094 pool: deep stack size for IV ULT - b26 (DAOS-17094 pool: deep stack size for IV ULT - b26 #16046)
- DAOS-17205 ci: Fix python bandit check (DAOS-17205 ci: Fix python bandit check #16003) (DAOS-17205 ci: Fix python bandit check (#16003) #16052)
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. Signed-off-by: Phil Henderson <phillip.henderson@hpe.com>
With this change, a test with a hard-coded tier 0 scm class: ram configuration is replaced with storage: auto (an ftest abstraction). This will steer testing to use the correct class: dcpm on functional hardware clusters with PMEM. Also, the pool size is increased to avoid pool create failures that would happen in the new configuration, i.e., avoiding: "requested SCM capacity is too small". Before the change, scm class: ram was used with PMEM, and led to Argobots ULT stack overflows and segmentation faults observed when executing in its mem pool allocation logic. Signed-off-by: Kenneth Cain <kenneth.cain@hpe.com>
Document just the essentials Signed-off-by: Jeff Olivier <jolivier23@gmail.com> Co-authored-by: Dalton Bohning <dalton.bohning@hpe.com> DAOS-17204 ci: Update the pull request template (#16002) Add a reminder to enable the appropriate functional test stages in a PR. Signed-off-by: Phil Henderson <phillip.henderson@hpe.com>
Use deep stack size for IV ULT to avoid stack overflow. Signed-off-by: Fan Yong <fan.yong@hpe.com>
Errors are component not formatted correctly,Ticket number prefix incorrect,PR title is malformatted. See https://daosio.atlassian.net/wiki/spaces/DC/pages/11133911069/Commit+Comments,Unable to load ticket data |
…/2.6 Change-Id: Ic4f6d21248eb295185652df0be2a79e3242ae69b
4292006
to
ce7a690
Compare
jolivier23
approved these changes
Mar 11, 2025
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.