Increase auto-techsupport wait for Arista-720DT#25495
Open
Xichen96 wants to merge 1 commit into
Open
Conversation
Arista-720DT can need longer than the default timeout to publish a techsupport tarball after auto-techsupport is triggered. Extend the existing slow-platform wait policy to cover this platform. Signed-off-by: Xichen Lin <lukelin0907@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Why I did it
Fixes #25079.
test_auto_techsupportis flaky on slow platforms because the test waits for a new techsupport tarball after triggering auto-techsupport. For Arista-720DT, recent 202511 nightly failures hit the same signature described in #25079:Evidence checked while investigating 720DT nightlies:
SONiC.20251110.35for:test_rate_limit_intervaltest_max_limit[techsupport]9d5a100af0), so this is not explained by an image update.deploy-mg, the two target 720DT cases passed 10x locally, so the issue remains flaky/state-dependent rather than always reproducible.This PR follows the existing Nokia slow-platform handling by adding Arista-720DT to the slow techsupport platform list.
How I did it
Add
x86_64-arista_720dt_48sto the platforms that use a 900s wait for the techsupport tarball to appear.The default remains 600s for other platforms.
How to verify it
Ran syntax check:
Manual 720DT validation during investigation:
Result after
deploy-mg: 10 consecutive runs passed for the two target cases (20 test executions).Description for the changelog
Increase auto-techsupport tarball wait time for Arista-720DT platforms.