Opened 3 months ago

Last modified 12 days ago

#31543 assigned New feature

Default output buffering on in tests

Reported by: Adam (Chainz) Johnson Owned by: Aly yasser
Component: Testing framework Version: master
Severity: Normal Keywords:
Cc: Baptiste Mispelon Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Following #31370, the --buffer option is supported for both parallel and non-parallel tests.

I think we should default to turning it *on* for all users, and provide a --no-buffer option to disable this behaviour.

This will improve output for many users, and increase speed for those projects whose tests currently print a lot of output. It has the risk of breaking some workflows of extracting information from tests ˙using print(), but since the output is only hidden for passing tests, I think this should be fairly niche.

Change History (3)

comment:1 Changed 3 months ago by Ahmad Abdallah

+1 on making this change. As already pointed out, eliminating unnecessary output will increase the speed of running tests. The associated risk of not seeing a print statement can be easily dealt with by using the --no-buffer option.

This will remove a lot of unnecessary clutter.

Last edited 3 months ago by Ahmad Abdallah (previous) (diff)

comment:2 Changed 3 months ago by Ahmad Abdallah

Triage Stage: UnreviewedAccepted

comment:3 Changed 12 days ago by Aly yasser

Owner: changed from nobody to Aly yasser
Status: newassigned
Note: See TracTickets for help on using tickets.
Back to Top