[sonic test] introduce a repeat harness#397
Closed
yxieca wants to merge 1 commit intosonic-net:masterfrom
Closed
Conversation
Introduce a test harness that repeats a user defined task list n times. By default, n is 10, user can override n with -extra-vars 'test_iterations=<num>'
auspham
pushed a commit
to auspham/sonic-mgmt
that referenced
this pull request
Jun 27, 2025
…ew SFP API naming. (sonic-net#397) Update get_transceiver_bulk_status to match the new SFP API naming. In sfp.py call get_transceiver_dom_real_value instead of get_transceiver_bulk_status. The change is according to https://github.com/sonic-net/sonic-platform-common/pull/556/files <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: Fixes # (issue) ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [x] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 ### Approach #### What is the motivation for this PR? Update in the SFP API of renaming the get_transceiver_bulk_status function to get_transceiver_dom_real_value. #### How did you do it? Update get_transceiver_bulk_status in sfp.py file to call the new function name. #### How did you verify/test it? Rerun successfully. #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…tomatically (sonic-net#19317) src/sonic-linux-kernel * 58d3bf5 - (HEAD -> 202205, origin/202205) [ci] Migrate to sonicbld1es agent pool. (sonic-net#397) (4 weeks ago) [Liu Shilong]
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…tomatically (sonic-net#19318) #### Why I did it src/sonic-linux-kernel ``` * 152aa10 - (HEAD -> 202305, origin/202305) Fix optoe's write_max when using native i2c driver (sonic-net#401) (14 hours ago) [Prince George] * ac4a1db - [ci] Migrate to sonicbld1es agent pool. (sonic-net#397) (sonic-net#403) (19 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
1 participant
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.
Approach
How did you do it?
Introduce a test harness that repeats a user defined task list n times.
By default, n is 10, user can override n with
-extra-vars 'test_iterations='
How did you verify/test it?
I needed this infrastructure to repeat some test cases continuously.
Known limitation:
The way ansible-playbook works is that the repeat_tasks.yml will be included times. So when n gets bigger, the time to include becomes very long. There might be other side effects with huge n.