[action] [PR:16119] Lower log level for message DUT type file doesn't exist
#16129
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
|
/azp run |
8 tasks
|
Original PR: #16119 |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-mgmt |
|
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:
This PR is to lower the log level for the message
DUT type file doesn't existfrom ERROR to INFO.The log message is annoying in the test result, and the log message is not monitored.
Type of change
Back port request
Approach
What is the motivation for this PR?
This PR is to lower the log level for the message
DUT type file doesn't existfrom ERROR to INFO.How did you do it?
Change the log level.
How did you verify/test it?
The change is verified by running a test on a physical testbed.
Any platform specific information?
No.
Supported testbed topology if it's a new test case?
Not a new test case.
Documentation