[GCU] Shorten GCU ignored LA list#5645
Merged
wen587 merged 5 commits intosonic-net:masterfrom Jun 16, 2022
Merged
Conversation
qiluo-msft
previously approved these changes
Jun 6, 2022
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
qiluo-msft
approved these changes
Jun 16, 2022
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
2 participants
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: Shortlen GCU Log Analyzer ignored regex list
[still pending 06/01] wait for sonic-net/sonic-utilities#2145 to eliminate one more LA list
[pending] sonic-net/sonic-buildimage#10954 submodule update
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Shortlen GCU list based on issue fix.
How did you do it?
Eliminate LA on GCU test suite
How did you verify/test it?
Run test
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation