Re: A note about debugging TAP failures

From: Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: A note about debugging TAP failures
Date: 2017-04-24 15:19:48
Message-ID: CAMsr+YE31P6Aky+xh0Ss0EMKrs-wUpJZL+sJ=zQg9n9eHe=-7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24 April 2017 at 20:01, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

> I’m np Perl expert though so there might be better/cleaner ways to achieve
> this, in testing it seems to work though. rmtree() is supported at least since
> Perl 5.6 from what I can see.

I'd rather just have the 'make' target nuke the relevant tmp_check dir
before rerunning the tests. Right now it just deletes the logs.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-04-24 15:52:09 Re: Interval for launching the table sync worker
Previous Message Craig Ringer 2017-04-24 15:14:40 Re: OK, so culicidae is *still* broken