[bgp-scale-test] reorder test cases to avoid device unisolation test effect other tests#18256
Merged
Blueve merged 1 commit intosonic-net:masterfrom May 7, 2025
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Blueve
approved these changes
May 7, 2025
Collaborator
|
This can only be a short term solution. For long-term, we need a checker to ensure the ASIC DB is expected before we entering the test case. |
Collaborator
|
hi @w1nda , I wonder if you could help do a manual cherry pick to 202412? |
11 tasks
Collaborator
|
Cherry-pick PR to msft-202412: Azure/sonic-mgmt.msft#266 |
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…effect other tests (sonic-net#18256) What is the motivation for this PR? The device unisolation test will restart all ports on DUT, after all bgp routes were stable in FRR after ports restart, however, the routes may not stable in ASIC, so the member scale test will be affected. How did you do it? To avoid this, move the device unisolation test to the last. How did you verify/test it? Run test on DUT Signed-off-by: opcoder0 <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…effect other tests (sonic-net#18256) What is the motivation for this PR? The device unisolation test will restart all ports on DUT, after all bgp routes were stable in FRR after ports restart, however, the routes may not stable in ASIC, so the member scale test will be affected. How did you do it? To avoid this, move the device unisolation test to the last. How did you verify/test it? Run test on DUT Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…effect other tests (sonic-net#18256) What is the motivation for this PR? The device unisolation test will restart all ports on DUT, after all bgp routes were stable in FRR after ports restart, however, the routes may not stable in ASIC, so the member scale test will be affected. How did you do it? To avoid this, move the device unisolation test to the last. How did you verify/test it? Run test on DUT Signed-off-by: Guy Shemesh <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…effect other tests (sonic-net#18256) What is the motivation for this PR? The device unisolation test will restart all ports on DUT, after all bgp routes were stable in FRR after ports restart, however, the routes may not stable in ASIC, so the member scale test will be affected. How did you do it? To avoid this, move the device unisolation test to the last. How did you verify/test it? Run test on DUT Signed-off-by: Guy Shemesh <[email protected]>
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.
Description of PR
Summary:
Fixes # (issue)
The device unisolation test will restart all ports on DUT, after all bgp routes were stable in FRR after ports restart, however, the routes may not stable in ASIC, so the member scale test will be affected. To avoid this, move the device unisolation test to the last.
Type of change
Back port request
Approach
What is the motivation for this PR?
The device unisolation test will restart all ports on DUT, after all bgp routes were stable in FRR after ports restart, however, the routes may not stable in ASIC, so the member scale test will be affected.
How did you do it?
To avoid this, move the device unisolation test to the last.
How did you verify/test it?
Run test on DUT
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation