Tom Lane wrote:
> Michael Paquier <michael.paqu...@gmail.com> writes:
> > On Thu, Dec 3, 2015 at 12:19 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> >> BTW, not the fault of this patch in particular, but this example points
> >> up the complaint I've had right along about how opaque TAP test failures
> >> are. How did you dig down to see that error message?
>
> > Well, it showed up on my terminal...
>
> Not on mine, as per the extract I showed. Probably a Perl version
> difference, but I don't think we can exactly write off RHEL6 as an
> uninteresting obsolete distribution. (The Perl here is 5.10.1.)
Hmm, maybe a selinux policy or something like that is preventing some
system call from working, and this causes a Perl call to fail which we
may be failing to report; for instance we have
open(ORIG_STDOUT, ">&STDOUT");
in TestLib.pm's INIT block, without an "or die" which would let us know
that it failed.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
