do not propagate to root logger from report.logger #1087
Merged
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.
Bug / Requirement Description
The report logger is a child of the root logger currently. Normally the root logger does not have any handler in tp runs, so any log meant to the report is not logged to the logfile/stdout.
It could happen that a user or other libraries sets up root logger to emmmit logs to stdout/stderr so report logs appear there as well, causing noise.
Solution description
Do not propagate from report logger to the root logger
Checklist: