From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: failures in t/031_recovery_conflict.pl on CI |
Date: | 2022-05-06 15:58:27 |
Message-ID: | 20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2022-05-05 23:57:28 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2022-05-05 23:36:22 -0400, Tom Lane wrote:
> >> So I reluctantly vote for removing 031_recovery_conflict.pl in the
> >> back branches for now, with the expectation that we'll fix the
> >> infrastructure and put it back after the current release round
> >> is done.
>
> > What about instead marking the flapping test TODO? That'd still give us most
> > of the coverage...
>
> Are you sure there's just one test that's failing? I haven't checked
> the buildfarm history close enough to be sure of that. But if it's
> true, disabling just that one would be fine (again, as a stopgap
> measure).
I looked through all the failures I found and it's two kinds of failures, both
related to the deadlock test. So I'm thinking of skipping just that test as in
the attached.
Working on committing / backpatching that, unless somebody suggests changes
quickly...
Greetings,
Andres Freund
Attachment | Content-Type | Size |
---|---|---|
disable-flapping-031-recovery-conflict.diff | text/x-diff | 701 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-05-06 16:12:19 | Re: failures in t/031_recovery_conflict.pl on CI |
Previous Message | Nathan Bossart | 2022-05-06 15:52:45 | Re: Possible corruption by CreateRestartPoint at promotion |