[action] [PR:16301] [loganalyzer] Ignore pmon#stormond iSmart binary format ERR log #16342
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
…c-net#16301) What is the motivation for this PR? Due to known issue sonic-net/sonic-buildimage#21319, ignore the ERR logs in loganalyzer. How did you do it? Update loganalyzer ignore file. How did you verify/test it? Verified on Nokia-7215 DUT, confirmed testcase can ignore this ERR log. Any platform specific information? Fix for Marvell-Armhf platform.
|
/azp run |
9 tasks
|
Original PR: #16301 |
|
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:
Due to known issue sonic-net/sonic-buildimage#21319, ignore the ERR logs in loganalyzer.
Type of change
Back port request
Approach
What is the motivation for this PR?
Due to known issue sonic-net/sonic-buildimage#21319, ignore the ERR logs in loganalyzer.
How did you do it?
Update loganalyzer ignore file.
How did you verify/test it?
Verified on Nokia-7215 DUT, confirmed testcase can ignore this ERR log.
Any platform specific information?
Fix for Marvell-Armhf platform.
Supported testbed topology if it's a new test case?
Documentation