-
Notifications
You must be signed in to change notification settings - Fork 741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dualtor] Fix snmp/* tests failure on fixture teardown #15529
Merged
StormLiangMS
merged 1 commit into
sonic-net:master
from
vkjammala-arista:fix-snmp-fixture-failures
Nov 15, 2024
Merged
[dualtor] Fix snmp/* tests failure on fixture teardown #15529
StormLiangMS
merged 1 commit into
sonic-net:master
from
vkjammala-arista:fix-snmp-fixture-failures
Nov 15, 2024
Conversation
This file contains 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
PR#15359 has introduced a "yield" statement inside the for loop of duthosts which is causing fixture teardown to fail with "Failed: fixture function has more than one 'yield'" message. Fix is to move "yield" statement out of this for loop and do config rollback in a seperate for loop of duthosts.
This was referenced Nov 13, 2024
vperumal
approved these changes
Nov 13, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM |
lolyu
approved these changes
Nov 14, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/azp run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Nov 15, 2024
Approach What is the motivation for this PR? sonic-net#15359 has introduced a "yield" statement inside the for loop of duthosts which is causing fixture teardown to fail with Failed: fixture function has more than one 'yield' message. How did you do it? Move "yield" statement out of this for loop of duthosts and do config rollback in a seperate for loop of duthosts. How did you verify/test it? Ran tests under snmp folder and tests are passing on Arista-7260CX3-D108C8 platform. Any platform specific information?
Cherry-pick PR to 202405: #15575 |
8 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Nov 15, 2024
Approach What is the motivation for this PR? #15359 has introduced a "yield" statement inside the for loop of duthosts which is causing fixture teardown to fail with Failed: fixture function has more than one 'yield' message. How did you do it? Move "yield" statement out of this for loop of duthosts and do config rollback in a seperate for loop of duthosts. How did you verify/test it? Ran tests under snmp folder and tests are passing on Arista-7260CX3-D108C8 platform. Any platform specific information?
mssonicbld
added
Included in 202405 branch
and removed
Created PR to 202405 branch
labels
Nov 15, 2024
sreejithsreekumaran
pushed a commit
to sreejithsreekumaran/sonic-mgmt
that referenced
this pull request
Nov 15, 2024
Approach What is the motivation for this PR? sonic-net#15359 has introduced a "yield" statement inside the for loop of duthosts which is causing fixture teardown to fail with Failed: fixture function has more than one 'yield' message. How did you do it? Move "yield" statement out of this for loop of duthosts and do config rollback in a seperate for loop of duthosts. How did you verify/test it? Ran tests under snmp folder and tests are passing on Arista-7260CX3-D108C8 platform. Any platform specific information?
yutongzhang-microsoft
pushed a commit
to yutongzhang-microsoft/sonic-mgmt
that referenced
this pull request
Nov 21, 2024
Approach What is the motivation for this PR? sonic-net#15359 has introduced a "yield" statement inside the for loop of duthosts which is causing fixture teardown to fail with Failed: fixture function has more than one 'yield' message. How did you do it? Move "yield" statement out of this for loop of duthosts and do config rollback in a seperate for loop of duthosts. How did you verify/test it? Ran tests under snmp folder and tests are passing on Arista-7260CX3-D108C8 platform. Any platform specific information?
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.
Description of PR
Summary: Move
yield
statement out of for loop in snmp fixturesetup_check_snmp_ready
Fixes # https://github.com/aristanetworks/sonic-qual.msft/issues/307
Type of change
Back port request
Approach
What is the motivation for this PR?
#15359 has introduced a "yield" statement inside the for loop of duthosts which is causing fixture teardown to fail with
Failed: fixture function has more than one 'yield'
message.How did you do it?
Move "yield" statement out of this for loop of duthosts and do config rollback in a seperate for loop of duthosts.
How did you verify/test it?
Ran tests under
snmp
folder and tests are passing onArista-7260CX3-D108C8
platform.Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation