DAOS-18676 test: DO NOT LAND debug TestPool.disconnect delays#17736
Draft
DAOS-18676 test: DO NOT LAND debug TestPool.disconnect delays#17736
Conversation
|
Ticket title is 'rebuild/continues_after_stop.py test timeout during teardown' |
Collaborator
|
Test stage Test RPMs on EL 9.6 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos/job/PR-17736/1/display/redirect |
Adjust engine logmasks to DEBUG while disconnecting from the pool created in the test_continuous_after_stop test. Since the disconnect portion of TestPool.destroy() seems to always be delayed by 1 or 2 minutes. Skip-unit-tests: true Skip-fault-injection-test: true Skip-test-el-9.6--rpms: true Skip-test-el-9.6-rpms: true Test-tag: test_continuous_after_stop Test-repeat: 10 Signed-off-by: Kenneth Cain <kenneth.cain@hpe.com>
7275197 to
254e771
Compare
This file contains hidden or 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
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.
Adjust engine logmasks to DEBUG while disconnecting from the pool created in the test_continuous_after_stop test. Since the disconnect portion of TestPool.destroy() seems to always be delayed by 1 or 2 minutes.
Skip-unit-tests: true
Skip-fault-injection-test: true
Test-tag: test_continuous_after_stop
Test-repeat: 10
Steps for the author:
After all prior steps are complete: