Re: Show backtrace when tap tests fail

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Show backtrace when tap tests fail
Date: 2017-09-20 03:13:14
Message-ID: CAMsr+YGDRiaDTU7_Bj23dzf1uoRdjP7Qc5eBbrG3L4+eyqe4RA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20 September 2017 at 06:36, David Steele <david(at)pgmasters(dot)net> wrote:

>
> I just use:
>
> $SIG{__DIE__} = sub {Carp::confess @_};
>

That's what I patched into my TestLib.pm too, until I learned of
Carp::Always.

I'd rather have Carp::Always, but it's definitely an OK fallback.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2017-09-20 03:34:29 Re: Page Scan Mode in Hash Index
Previous Message Craig Ringer 2017-09-20 03:10:41 Re: src/test/subscription/t/002_types.pl hanging on particular environment