Re: IPC::Run::time[r|out] vs our TAP tests

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: IPC::Run::time[r|out] vs our TAP tests
Date: 2026-02-03 22:32:22
Message-ID: 202602032231.t3s7bwhg75yb@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Feb-20, Daniel Gustafsson wrote:

> > On 20 Feb 2025, at 14:06, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> > Actually, since ok() and friends return true iff the test succeeds, instead of
> > + ok(! $self->{timeout}->is_expired, 'psql query_until did not time out');
> > + return undef if $self->{timeout}->is_expired;
> > you can avoid doing the same test twice and say:
> > ok(! $self->{timeout}->is_expired, 'psql query_until did not time out') || return undef;
> > although for slightly technical reasons perlcritic disapproves of "return undef" and prefers that you just write a bare "return" so we should also fix that.
> > Sorry for taking a second bite at the cherry.
>
> Not at all, I agree that this is an improvement so fixed in the attached along
> with a fresh pgperltidy.

Hello, was this forgotten, or is there some other reason why the
commitfest entry is still open?
https://commitfest.postgresql.org/patch/4959/

Thanks,

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"La vida es para el que se aventura"

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2026-02-03 22:32:51 Re: Odd code around ginScanToDelete
Previous Message Tom Lane 2026-02-03 22:29:46 Re: Decoupling our alignment assumptions about int64 and double