DAOS-10915 csum: Scrubbing Cleanup
When the csum scrubbing feature branch landed, there where some minor style and text items that needed to be resolved. This change resolves those.
Signed-off-by: Ryon Jensen [email protected]
Before requesting gatekeeper:
- [ ] Two review approvals and any prior change requests have been resolved.
- [ ] Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
- [ ] Commit messages follows the guidelines outlined here.
- [ ] Any tests skipped by the ticket being addressed have been run and passed in the PR.
Gatekeeper:
- [ ] You are the appropriate gatekeeper to be landing the patch.
- [ ] The PR has 2 reviews by people familiar with the code, including appropriate watchers.
- [ ] Githooks were used. If not, request that user install them and check copyright dates.
- [ ] Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
- [ ] All builds have passed. Check non-required builds for any new compiler warnings.
- [ ] Sufficent testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
- [ ] If applicable, the PR has addressed any potential version compatibility issues.
- [ ] Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
- [ ] Extra checks if forced landing is requested
- [ ] Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
- [ ] No new NLT or valgrind warnings. Check the classic view.
- [ ] Quick-build or Quick-functional is not used.
- [ ] Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.
Bug-tracker data: Ticket title is 'Checksum Scrubbing Feature Branch Landing Cleanup' Status is 'In Review' Labels: 'checksum_scrubber' https://daosio.atlassian.net/browse/DAOS-10915
Test stage Functional Hardware Small completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-10576/1/testReport/(root)/
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10576/1/execution/node/1085/log
I think I fixed the flake8 error.
Not sure why spell check failed on a file I didn't touch??
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10576/3/execution/node/1130/log
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10576/4/execution/node/1130/log
Test failures appear to be DAOS-11936
Requesting forced-landing by @daos-stack/daos-gatekeeper because of known test failures.
poke @daos-stack/daos-gatekeeper
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10576/5/execution/node/1130/log
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10576/5/execution/node/1083/log
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-10576/6/display/redirect
Test stage Functional Hardware Small completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-10576/6/display/redirect
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-10576/6/display/redirect
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10576/7/execution/node/1083/log
Known test failure: https://daosio.atlassian.net/browse/DAOS-12031. Requesting force landing.
Had a conflict so merged with master. Rebuilding ...
On the previous build, everything passed. I had to remove a duplicate from a list in the jira_query script so used pragmas to not build or test. This is ready to land.
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10576/12/execution/node/1130/log
Test failure is known
- test_nvme_pool_extend: https://daosio.atlassian.net/browse/DAOS-12073
Requesting force landing