public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Tom Lane <[email protected]>
To: Paul Jungwirth <[email protected]>
Cc: jian he <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: vignesh C <[email protected]>
Subject: Re: SQL:2011 application time
Date: Mon, 27 Jan 2025 16:47:35 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<5f0c25de-2c13-4fb5-a4df-a1e03c43cd14@illuminatedcomputin! g.com>
<[email protected]>
<[email protected]>
<[email protected]>
<bca3e7e6-ac1f-476d-9725-d6aec9100ed0@illumin! atedcomputing.com>
<[email protected]>
<c46c47dc! [email protected]>
<[email protected]>
On 24.01.25 03:55, Tom Lane wrote:
> Paul Jungwirth <[email protected]> writes:
>> On 1/23/25 15:28, Tom Lane wrote:
>>> I've only noticed the two, but I did not mount an aggressive search.
>>> It's possible that there were failures before 1772d554b0, since I
>>> now see that the diff is in a test case that is older than that.
>
>> Okay, I'll keep in mind that it could be older.
>
> I've now run an exhaustive search through the last three months of
> buildfarm runs, and found just one additional instance of the same
> failure. The three matches are
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2025-01-22%2005%3A49%3A...
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-01-22%2001%3A29%3A35
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2025-01-22%2001%3A17%3A14
>
> Since those are all post-1772d554b0, it's difficult to avoid the
> conclusion that that either introduced the error or allowed a
> pre-existing problem to become visible.
I found a few more in the bowels of various Cirrus CI jobs:
https://cirrus-ci.com/task/5125479033733120
->
https://api.cirrus-ci.com/v1/artifact/task/5125479033733120/testrun/build/testrun/regress/regress/re...
https://cirrus-ci.com/task/4562529080311808
->
https://api.cirrus-ci.com/v1/artifact/task/4562529080311808/log/src/test/recovery/tmp_check/regressi...
https://cirrus-ci.com/task/5985049025183744
->
https://api.cirrus-ci.com/v1/artifact/task/5985049025183744/log/src/bin/pg_upgrade/tmp_check/regress...
https://cirrus-ci.com/task/4702566639992832
->
https://api.cirrus-ci.com/v1/artifact/task/4702566639992832/log/src/test/recovery/tmp_check/regressi...
view thread (23+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: SQL:2011 application time
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox