fix: add concurrent run for config_reload pc_test_lag #15721
Conversation
This file contains 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
auspham
force-pushed
the
austinpham/30112211-investigate-resolve-pc-test-lag-2
branch
from
128216a
to
014dffe
Compare
Signed-off-by: Austin Pham <[email protected]>
auspham
force-pushed
the
austinpham/30112211-investigate-resolve-pc-test-lag-2
branch
from
014dffe
to
ac178dd
Compare
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.
Description of PR
Currently, pc/test_lag_2 is having timeout in teardown with the default timeout of 300 seconds.
Since by default the thread_count = 2, which means at maximum, only 2 available thread can be used to run config_reload in DUT. Which means only 2 DUT are config_reload at a time.
This will be slow and exceed 300 seconds.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
we should specify the
thread_countto be the same number of duthost so that they're all config_reload in concurrent.How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation