daos icon indicating copy to clipboard operation
daos copied to clipboard

DAOS-16670 test: multiple_delete.py with DAOS-16445

Open shimizukko opened this issue 1 year ago • 4 comments

Looks like DAOS-16445 and PR 14999 are causing multiple_delete.py to fail. Run the test at that commit.

Skip-unit-tests: true Skip-fault-injection-test: true Skip-func-hw-test-medium-md-on-ssd: false Test-tag: test_multiple_container_delete Test-repeat: 5

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.
  • [ ] Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • [ ] 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 owners.
  • [ ] 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.
  • [ ] Sufficient 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.

shimizukko avatar Oct 22 '24 06:10 shimizukko

Ticket title is 'container/multiple_delete.py:MultipleContainerDelete.test_multiple_container_delete - SCM space wasn't recovered!' Status is 'Open' Labels: 'ci_master_weekly,weekly_test' https://daosio.atlassian.net/browse/DAOS-16670

github-actions[bot] avatar Oct 22 '24 06:10 github-actions[bot]

To block accidental landing since this is just a test. Did you mean to mark this as a Draft?

Yes, but I realized that there's no way to convert it to a draft after creating it.

shimizukko avatar Oct 22 '24 20:10 shimizukko

Yes, but I realized that there's no way to convert it to a draft after creating it.

Under "Reviewers" there is the Still in progress? Convert to draft option.

phender avatar Oct 22 '24 20:10 phender

Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-15360/1/testReport/

daosbuild1 avatar Oct 22 '24 22:10 daosbuild1