Suppress "Computing stats ..." output lines

[MMesch]

I have many pytest-benchmarks in my unit tests and I get many many lines of output from pytest-benchmark on the CI. Would it be possible to add an option to suppress it, to see just the summary?

The problematic lines are:

Computing stats ...
Computing stats ... group 1/1
Computing stats ... group 1/1: min
Computing stats ... group 1/1: min (1/25)
Computing stats ... group 1/1: min (2/25)
Computing stats ... group 1/1: min (3/25)
Computing stats ... group 1/1: min (4/25)
Computing stats ... group 1/1: min (5/25)
Computing stats ... group 1/1: min (6/25)
Computing stats ... group 1/1: min (7/25)
Computing stats ... group 1/1: min (8/25)
Computing stats ... group 1/1: min (9/25)
Computing stats ... group 1/1: min (10/25)
Computing stats ... group 1/1: min (11/25)
Computing stats ... group 1/1: min (12/25)
Computing stats ... group 1/1: min (13/25)
Computing stats ... group 1/1: min (14/25)
Computing stats ... group 1/1: min (15/25)
Computing stats ... group 1/1: min (16/25)
Computing stats ... group 1/1: min (17/25)
Computing stats ... group 1/1: min (18/25)
Computing stats ... group 1/1: min (19/25)
Computing stats ... group 1/1: min (20/25)
Computing stats ... group 1/1: min (21/25)
Computing stats ... group 1/1: min (22/25)
Computing stats ... group 1/1: min (23/25)

[...]

Computing stats ... group 1/1: ops: rounds (17/25)
Computing stats ... group 1/1: ops: rounds (18/25)
Computing stats ... group 1/1: ops: rounds (19/25)
Computing stats ... group 1/1: ops: rounds (20/25)
Computing stats ... group 1/1: ops: rounds (21/25)
Computing stats ... group 1/1: ops: rounds (22/25)
Computing stats ... group 1/1: ops: rounds (23/25)
Computing stats ... group 1/1: ops: rounds (24/25)
Computing stats ... group 1/1: ops: rounds (25/25)
Computing stats ... group 1/1: ops: iterations
Computing stats ... group 1/1: ops: iterations (1/25)
Computing stats ... group 1/1: ops: iterations (2/25)
Computing stats ... group 1/1: ops: iterations (3/25)
Computing stats ... group 1/1: ops: iterations (4/25)
Computing stats ... group 1/1: ops: iterations (5/25)
Computing stats ... group 1/1: ops: iterations (6/25)
Computing stats ... group 1/1: ops: iterations (7/25)
Computing stats ... group 1/1: ops: iterations (8/25)
Computing stats ... group 1/1: ops: iterations (9/25)
Computing stats ... group 1/1: ops: iterations (10/25)
Computing stats ... group 1/1: ops: iterations (11/25)
Computing stats ... group 1/1: ops: iterations (12/25)
Computing stats ... group 1/1: ops: iterations (13/25)
Computing stats ... group 1/1: ops: iterations (14/25)
Computing stats ... group 1/1: ops: iterations (15/25)
Computing stats ... group 1/1: ops: iterations (16/25)
Computing stats ... group 1/1: ops: iterations (17/25)
Computing stats ... group 1/1: ops: iterations (18/25)
Computing stats ... group 1/1: ops: iterations (19/25)
Computing stats ... group 1/1: ops: iterations (20/25)
Computing stats ... group 1/1: ops: iterations (21/25)
Computing stats ... group 1/1: ops: iterations (22/25)
Computing stats ... group 1/1: ops: iterations (23/25)
Computing stats ... group 1/1: ops: iterations (24/25)
Computing stats ... group 1/1: ops: iterations (25/25)

[ionelmc]

I suppose we could detect that stdout ain't attached to a pty and don't do the progress stuff (not yet another option). How about that?

[ionelmc]

Or we could do the progress stuff only if --benchmark-verbose is used ...

[jeremyschiemann]

+1

[pkupisie]

+1

[tefra]

+1