[test_platform_info] Fix issues: sometimes the expected error log is not caught by log analyzer#2575
Merged
liat-grozovik merged 1 commit intosonic-net:masterfrom Nov 24, 2020
Conversation
3 tasks
keboliu
approved these changes
Nov 24, 2020
liat-grozovik
approved these changes
Nov 24, 2020
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
Update sonic-utilities submodule pointer to include the following: * c9ed09d [202205] [sonic_installer] use /etc/resolv.conf from the host when migrating packages (sonic-net#2573) ([sonic-net#2575](sonic-net/sonic-utilities#2575)) Signed-off-by: dprital <[email protected]>
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
3 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:
Fixes issue: sometimes the expected error log is not caught by log analyzer. There is chance that the expect error log is in syslog but not caught by log analyzer, move the log analyzer to outter level to make sure it caught the expected log.
Type of change
Approach
What is the motivation for this PR?
Fixes issue: sometimes the expected error log is not caught by log analyzer.
How did you do it?
Move the log analyzer to outter level to make sure it caught the expected log
How did you verify/test it?
Manually run the regression
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
N/A
Documentation