Skip to content

Increase auto-techsupport wait for Arista-720DT#25495

Open
Xichen96 wants to merge 1 commit into
masterfrom
xichen96/showtech-720dt-timeout
Open

Increase auto-techsupport wait for Arista-720DT#25495
Xichen96 wants to merge 1 commit into
masterfrom
xichen96/showtech-720dt-timeout

Conversation

@Xichen96

Copy link
Copy Markdown
Contributor

Why I did it

Fixes #25079.

test_auto_techsupport is 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:

AssertionError: New expected techsupport file was not generated

Evidence checked while investigating 720DT nightlies:

  • Public issue Flaky: show_techsupport.test_auto_techsupport - Techsupport file not generated in time #25079 already tracks this failure class and lists Arista-720DT as affected.
  • Kusto showed 720DT m0 failures on SONiC.20251110.35 for:
    • test_rate_limit_interval
    • test_max_limit[techsupport]
  • The failing and passing 720DT runs used the same image commit (9d5a100af0), so this is not explained by an image update.
  • We also checked mgmt commits in the fail/pass window and did not find a show_techsupport/loganalyzer/sanity change that would explain the difference.
  • After 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_48s to 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:

python3 -m py_compile tests/show_techsupport/test_auto_techsupport.py

Manual 720DT validation during investigation:

./run_tests.sh -n testbed-bjw2-can-720dt-6 -i ../ansible/veos,../ansible/bjw2 -u -x -a False -t m0,any \
  -c "show_techsupport/test_auto_techsupport.py::TestAutoTechSupport::test_rate_limit_interval" \
  -c "show_techsupport/test_auto_techsupport.py::TestAutoTechSupport::test_max_limit[techsupport]"

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.

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>
@Xichen96 Xichen96 added the Request for 202511 branch Request to backport a change to 202511 branch label Jun 19, 2026
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Request for 202511 branch Request to backport a change to 202511 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flaky: show_techsupport.test_auto_techsupport - Techsupport file not generated in time

2 participants