From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TAP / recovery-test fs-level backups, psql enhancements etc |
Date: | 2016-03-02 07:51:48 |
Message-ID: | 4201.1456905108@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> Yes, that's the problem. Instead of using details(), summary() is
>> enough actually. And it is enough to let caller know the failure when
>> just one test has been found as not passing. See attached.
> This one works for me on RHEL6. Pushed; we'll see if the older
> buildfarm members like it.
I don't normally run the TAP tests on "prairiedog", because it's
too $!*&@ slow, but trying that manually seems to work. That's
the Perl 5.8.6 that Apple shipped with OS X 10.4 ... if there's
anything older in our buildfarm, I don't know about it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2016-03-02 08:33:25 | Re: Freeze avoidance of very large table. |
Previous Message | wcting | 2016-03-02 07:25:24 | Re: redo failed in physical streaming replication while stopping the master server |