DAOS-19121 tests: increase timeout for verify_dtx - #18800
Open
Nasf-Fan wants to merge 1 commit into
Open
Conversation
The test verifies DTX metrics with mdtest against kinds of object classes. During the test, some factors may cause test to be slow, such as (VOS/EC) aggregation, backend TX overhead under md-on-ssd mode, network congestion, and so on. Anyway, performance is not the test purpose. So increasing the max allowed test time from 600 to 800 seconds to avoid unexpected timeout. Test-tag-hw-large: test_verify_dtx_metrics Signed-off-by: Fan Yong <fan.yong@hpe.com>
|
Ticket title is 'pool/verify_dtx.py:VerifyDTXMetrics.test_verify_dtx_metrics - test timeout' |
Contributor
Author
|
Required CI tests passed. |
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
1 participant
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.
The test verifies DTX metrics with mdtest against kinds of object classes. During the test, some factors may cause test to be slow, such as (VOS/EC) aggregation, backend TX overhead under md-on-ssd mode, network congestion, and so on. Anyway, performance is not the test purpose. So increasing the max allowed test time from 600 to 800 seconds to avoid unexpected timeout.
Test-tag-hw-large: test_verify_dtx_metrics
Steps for the author:
After all prior steps are complete: