Re: making pg_regress less noisy by removing boilerplate - Mailing list pgsql-hackers

From Tom Lane
Subject Re: making pg_regress less noisy by removing boilerplate
Date
Msg-id 517976.1645463142@sss.pgh.pa.us
Whole thread Raw
In response to making pg_regress less noisy by removing boilerplate  (Andres Freund <andres@anarazel.de>)
Responses Re: making pg_regress less noisy by removing boilerplate  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> When running check-world, a good chunk of the output is just pg_regress
> boilerplate. It doesn't matter when running tests individually or for tests
> with a lot of individual tests like the main regression tests. But for lots of
> the rest it is noisy. These days there are many more regression tests than
> there used to be when the output was designed...

Also, those steps typically run a lot faster than they did then
(both software speedups, and most people use better hardware).
We no longer need that output to reassure ourselves that progress
is being made.

> It seems we could [ combine printouts ]

How about going further, and just not print *any* of this overhead
stuff, except maybe the "running on port 51696 with PID 1156405"
line (and I'm not too wedded to that)?  It is only interesting
if something fails.  For that, maybe if there's a failure we
could print "while running text-of-command-here" after the fact.

It'd also be a good idea to start using "make -s" by default for the
preparatory steps.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Add checkpoint and redo LSN to LogCheckpointEnd log message
Next
From: Tom Lane
Date:
Subject: Re: show schema.collate in explain(verbose on)