Re: IPC::Run::time[r|out] vs our TAP tests - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: IPC::Run::time[r|out] vs our TAP tests
Date
Msg-id 202602032231.t3s7bwhg75yb@alvherre.pgsql
Whole thread Raw
In response to Re: IPC::Run::time[r|out] vs our TAP tests  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: IPC::Run::time[r|out] vs our TAP tests
List pgsql-hackers
On 2025-Feb-20, Daniel Gustafsson wrote:

> > On 20 Feb 2025, at 14:06, Andrew Dunstan <andrew@dunslane.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"



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Decoupling our alignment assumptions about int64 and double
Next
From: Alexander Korotkov
Date:
Subject: Re: Odd code around ginScanToDelete