Exclude stdout/stderr log sections when --report-log-exclude-logs-on-passed-tests is given #96
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.
I noticed that the size of the log file written by this plugin was 100MB+, and sections like "Captured stderr call" were included, even though I'd specified the
--report-log-exclude-logs-on-passed-testsflag.Would it make sense to make the flag also exclude captured outputs too, in addition to captured logs?
If I'm reading it right, junitxml's
log_passing_testssetting covers both stdout/stderr outputs and logging outputs:https://github.com/pytest-dev/pytest/blob/9.0.2/src/_pytest/junitxml.py#L159-L180