Allow progress console_output_style even when capture=no #10737
Labels
plugin: capture
related to the capture builtin plugin
type: performance
performance or memory problem/improvement
What's the problem this feature will solve?
When running large test suites like
pyca/cryptography
we see significant (up to 40%!) slowdown on some jobs when capturing is enabled. However, enabling capture disables "progress" , which in turn results in extraordinarily long lines on GitHub Actions, which breaks browsers' ability to load CI output.Describe the solution you'd like
In #3038 the "progress" output was disabled when capture=no (defaulting back to classic) because any extraneous stdout/stderr from the tests will mess up the output. However, for users who are willing to risk accidentally leaving code that might write to stdout/stderr it would be great to support a flag that would re-enable progress info.
Alternative Solutions
The text was updated successfully, but these errors were encountered: