Re: [PATCH] Reduce src/test/recovery verbosity - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [PATCH] Reduce src/test/recovery verbosity
Date
Msg-id 20170329181737.GM9812@tamriel.snowman.net
Whole thread Raw
In response to [HACKERS] [PATCH] Reduce src/test/recovery verbosity  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [PATCH] Reduce src/test/recovery verbosity  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
* Dagfinn Ilmari Mannsåker (ilmari@ilmari.org) wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>
> > On 3/28/17 23:42, Michael Paquier wrote:
> >> src/bin/pg_dump and src/test/modules/test_pgdump generate too much
> >> output. If we could get tests to only print the final result, like how
> >> many tests done and how many have passed, things would be much
> >> friendlier.
> >
> > There are options to change the verbosity of things.
> >
> > I don't think I would like changing the default verbosity.  At least the
> > precedent from the pg_regress type tests is that there should be some
> > action on the screen as things run.
>
> Non-verbose prove still lists each test script, it just doesn't list
> each individual test within the script.

I agree that it'd be better to just show the per-script results rather
than every little test result because it's just too much.

If there's a way to change the verbosity for just those scripts, I'd be
happy to do that, if we're unable to agree on reducing it across the
board..

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)
Next
From: Stephen Frost
Date:
Subject: Re: Schedule and Release Management Team for PG10