Set level of logger dataplane to error
#1838
Merged
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
When we run the fdb/test_fdb.py script, the `dataplane` logger generats **too** much log messages at warning level. This change sets log level of the `dataplne` logger to error to filter out the warning messages. Signed-off-by: Xin Wang <xiwang5@microsoft.com>
bingwang-ms
approved these changes
Jul 1, 2020
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:
Fixes # (issue)
When we run the fdb/test_fdb.py script, the
dataplanelogger generatstoo much log messages at warning level. Previously we have increased
log level of the
dataplanelogger to warning. It is still not enough.This change sets log level of the
dataplnelogger to error to filter outthe warning messages as well.
Type of change
Approach
What is the motivation for this PR?
To filter out too much unnecessary warning level log messages generated by the
dataplanelogger when running the fdb/test_fdb.py script.How did you do it?
Grab the
dataplanelogger in tests/conftest.py and set its log level to error.How did you verify/test it?
Test run the fdb/test_fdb.py script, set --log-cli-level to info. No more unnecessary log messages.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation