Re: [HACKERS] Time to change pg_regress diffs to unified by default? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Time to change pg_regress diffs to unified by default?
Date
Msg-id 40c5c12f-adad-fc86-7d43-ff7c535356ed@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Time to change pg_regress diffs to unified by default?  (Christoph Berg <myon@debian.org>)
Responses Re: [HACKERS] Time to change pg_regress diffs to unified by default?
List pgsql-hackers
On 2019-02-15 16:05, Christoph Berg wrote:
> Re: Andrew Gierth 2019-02-15 <874l95m8w7.fsf@news-spur.riddles.org.uk>
>> Also while we're tweaking regression test output, would it be possible
>> to have some indicator of whether a test passed because a variant file
>> in the resultmap was ignored in favor of the standard result?
>>
>> The current system of silently ignoring the resultmap means that nobody
>> ever notices when resultmap entries become obsolete....
> 
> By the same argument, it should always print which variant file was
> used so determining which _N.out files are still in use is possible.

I would rather not overload the test output even more.  A test passes or
it doesn't.  If we need to collect additional information, let's think
about ways to do that separately.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Time to change pg_regress diffs to unified by default?
Next
From: "Matsumura, Ryo"
Date:
Subject: RE: SQL statement PREPARE does not work in ECPG