Skip to content
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

DAOS-16499 tests: Debug smoke #15163

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from
Draft

DAOS-16499 tests: Debug smoke #15163

wants to merge 4 commits into from

Conversation

liw
Copy link
Contributor

@liw liw commented Sep 20, 2024

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.

Copy link

Ticket title is 'soak/smoke.py: "pool destroy TestPool_1 --force --recursive" timedout'
Status is 'In Progress'
https://daosio.atlassian.net/browse/DAOS-16499

@daosbuild1
Copy link
Collaborator

Test stage Test RPMs on EL 8.6 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15163/2/execution/node/772/log

@daosbuild1
Copy link
Collaborator

Test stage Test RPMs on EL 8.6 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15163/3/execution/node/770/log

@daosbuild1
Copy link
Collaborator

Test stage Test RPMs on EL 8.6 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15163/4/execution/node/735/log

Introduce a simple type-checked vector template to gurt. See
D_VEC_DECLARE and D_VEC_DEFINE for its usage.

Signed-off-by: Li Wei <wei.g.li@intel.com>
Required-githooks: true
Introduce a non-production reference tracker mechanism for debugging
reference counting problems. See d_ref_tracker. Use this new mechanism
for ds_pool_child.

This tracking is only compiled in for non-release builds; there should
be no performance or memory overhead for release builds.

Signed-off-by: Li Wei <wei.g.li@intel.com>
Required-githooks: true
Use d_ref_tracker on ds_pool.

Signed-off-by: Li Wei <wei.g.li@intel.com>
Required-githooks: true
Test-tag: soak_smoke
Test-repeat: 5
Doc-only: false
Skip-unit-tests: true
Skip-fault-injection-test: true
Skip-test-centos-rpms: true
Allow-unstable-test: true
Signed-off-by: Li Wei <wei.g.li@intel.com>
Required-githooks: true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants