Re: Add SHELL_EXIT_CODE to psql - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Add SHELL_EXIT_CODE to psql
Date
Msg-id CA+hUKGLVQc5Ed9ARPpHwm-uuyuO7avbRPxRpnCMEZgcc3The9A@mail.gmail.com
Whole thread Raw
In response to Re: Add SHELL_EXIT_CODE to psql  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: Add SHELL_EXIT_CODE to psql
List pgsql-hackers
On Tue, Jan 31, 2023 at 9:23 AM Corey Huinker <corey.huinker@gmail.com> wrote:
>> Unfortunately, there is a fail in FreeBSD https://cirrus-ci.com/task/6466749487382528
>>
>> Maybe, this patch is need to be rebased?
>>
>
> That failure is in postgres_fdw, which this code doesn't touch.
>
> I'm not able to get to /tmp/cirrus-ci-build/build/testrun/postgres_fdw-running/regress/regression.out - It's not in
eitherof the browseable zip files and the 2nd zip file isn't downloadable, so it's hard to see what's going on.
 

Yeah, that'd be our current top flapping CI test[1].  These new
"*-running" tests (like the old "make installcheck") are only enabled
in the FreeBSD CI task currently, so that's why the failures only show
up there.  I see[2] half a dozen failures of the "fdw_retry_check"
thing in the past ~24 hours.

[1] https://www.postgresql.org/message-id/flat/20221209001511.n3vqodxobqgscuil%40awork3.anarazel.de
[2] http://cfbot.cputube.org/highlights/regress.html



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: [PATCH] Fix unbounded authentication exchanges during PQconnectPoll()
Next
From: Vladimir Churyukin
Date:
Subject: Re: Improving inferred query column names