Ignore Port Counter laganalyzer error in test_iface_namingmode #16073
+10
−0
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
Similar issue to sonic-net#12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process. Adding a loganalyzer ignore for this message to this test to fix.
|
/azp run |
|
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
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:
Loganalyzer error
ERR syncd#syncd: :- collectData: Failed to get stats of Port Counterin test_iface_namingmode.Similar issue to #12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process.
Adding a loganalyzer ignore for this message to this test, since we observe this error only with test_iface_namingmode.
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Confirmed this resolved test_iface_namingmode fails on our t2 testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation