| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inadequate traces in TAP tests |
| Date: | 2017-03-20 14:27:39 |
| Message-ID: | 3211f0c7-27c2-9c24-0c9e-e90f5c490051@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-20 14:28:30 | Re: free space map and visibility map |
| Previous Message | Stephen Frost | 2017-03-20 14:26:20 | Re: Inadequate traces in TAP tests |