[action] [PR:21582] fix: only disable route check for T2#21613
Merged
wangxin merged 1 commit intosonic-net:202511from Dec 12, 2025
Merged
[action] [PR:21582] fix: only disable route check for T2#21613wangxin merged 1 commit intosonic-net:202511from
wangxin merged 1 commit intosonic-net:202511from
Conversation
* fix: only disable route check for T2 Signed-off-by: Chenyang Wang <[email protected]> * Empty commit to re-trigger the pipeline Signed-off-by: Chenyang Wang <[email protected]> --------- Signed-off-by: Chenyang Wang <[email protected]>
12 tasks
Collaborator
Author
|
Original PR: #21582 |
Collaborator
Author
|
/azp run |
github-actions
bot
requested review from
ZhaohuiS,
rawal01,
saiarcot895,
wangxin and
xwjiang-ms
|
Azure Pipelines successfully started running 1 pipeline(s). |
wangxin
approved these changes
Dec 12, 2025
lakshmi-nexthop
pushed a commit
to lakshmi-nexthop/sonic-mgmt
that referenced
this pull request
Feb 11, 2026
…1613) Change the temporarily_disable_route_check fixture logic to only apply to T2 topology for now. What is the motivation for this PR? The current disable-and-enable routeCheck monitor logic is causing test flakiness on some non-T2 platforms (see sonic-net#16876 (comment)). Certain platforms require additional time to restart the routeCheck monitor, which can leave it inactive when the next test begins and result in false failures. We would like to address this issue urgently in this PR. In a follow-up PR, I will properly enhance the temporarily_disable_route_check fixture so that: Users can choose which topologies apply the disable-and-enable routeCheck behavior The fixture uses a wait_until() timeout to verify the routeCheck status is as expected before proceeding to the next step How did you do it? How did you verify/test it? I ran the updated login on a non-T2 platform (Mx) and can confirm it's working well: https://elastictest.org/scheduler/testplan/693272f7392767e9bf67e930 image I also verified the logic on T2 platform and can confirm it's still having this logic: https://elastictest.org/scheduler/testplan/6932767fbcc3fac23371a83c image Signed-off-by: Chenyang Wang <[email protected]> Co-authored-by: Chenyang Wang <[email protected]> Signed-off-by: Lakshmi Yarramaneni <[email protected]>
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…atically (sonic-net#21613) #### Why I did it src/sonic-utilities ``` * bbe29aee - (HEAD -> 202411, origin/202411) [show][interface] Add changes for show interface errors command (sonic-net#3749) (4 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
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
3 participants
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
Change the
temporarily_disable_route_checkfixture logic to only apply to T2 topology for now.Summary:
Fixes # (issue) Microsoft ADO 36101536
Type of change
Back port request
Approach
What is the motivation for this PR?
The current disable-and-enable routeCheck monitor logic is causing test flakiness on some non-T2 platforms (see #16876 (comment)). Certain platforms require additional time to restart the routeCheck monitor, which can leave it inactive when the next test begins and result in false failures. We would like to address this issue urgently in this PR.
In a follow-up PR, I will properly enhance the
temporarily_disable_route_checkfixture so that:wait_until()timeout to verify the routeCheck status is as expected before proceeding to the next stepHow did you do it?
How did you verify/test it?
I ran the updated login on a non-T2 platform (Mx) and can confirm it's working well:
https://elastictest.org/scheduler/testplan/693272f7392767e9bf67e930
I also verified the logic on T2 platform and can confirm it's still having this logic: https://elastictest.org/scheduler/testplan/6932767fbcc3fac23371a83c
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation