Re: [HACKERS] Inadequate traces in TAP tests - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [HACKERS] Inadequate traces in TAP tests
Date
Msg-id 3211f0c7-27c2-9c24-0c9e-e90f5c490051@2ndQuadrant.com
Whole thread Raw
In response to Re: [HACKERS] Inadequate traces in TAP tests  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

On 03/20/2017 10:08 AM, Tom Lane wrote:
> I am *absolutely* not in favor of adding anything to the scripts' routine
> output, because it will just make this problem worse by bloating the
> buildfarm logs even more.  What I'd like to see is for the scripts to
> always report something along the lines of "this is what I got, this is
> what I expected to get" --- but only when there is a failure.  The less
> output there is from a successful test, the better, IMO.
>
>             



The problem in the current instance is that the error occurred before it
ever tried to run a test. It died in the setup code for the test set.

cheers

andrew



-- 

Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Inadequate traces in TAP tests
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] free space map and visibility map