[action] [PR:18733] [CRM AVAILABLE] To enhance the crm tests for TD3 and Cisco devices#18761
Merged
mssonicbld merged 1 commit intosonic-net:202505from Jun 4, 2025
Merged
Conversation
…onic-net#18733) For TD3, the maximum number of nexthop groups is 255, which is below the minimum requirement of 256, resulting in test failures. To address this, TD3 should be added to SKU_NEXTHOP_THRESHOLDS. Additionally, some HWSKUs require more time for the crm command to become operational. To accommodate this, the wait time has been increased from 90 seconds to 360 seconds in worst case. What is the motivation for this PR? To fix the flaky failure on Cisco devices and the consistent failure on TD3 How did you do it? For TD3, add 255 as a threshold. Extend maximum wait time from 90 seconds to 360 seconds. How did you verify/test it? Run test on TD3 and Cisco devices.
11 tasks
Collaborator
Author
|
Original PR: #18733 |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
Summary:
Fixes # (issue)
For TD3, the maximum number of nexthop groups is 255, which is below the minimum requirement of 256, resulting in test failures. To address this, TD3 should be added to SKU_NEXTHOP_THRESHOLDS.
Additionally, some HWSKUs require more time for the crm command to become operational. To accommodate this, the wait time has been increased from 90 seconds to 360 seconds in worst case.
Type of change
Back port request
Approach
What is the motivation for this PR?
To fix the flaky failure on Cisco devices and the consistent failure on TD3
How did you do it?
How did you verify/test it?
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
N/A
Documentation