Re: Thomas Munro
> 2022), and then backpatched to all releases. They were disabled again
> in release branches 10-14 (discussion at
> https://postgr.es/m/3447060.1652032749@sss.pgh.pa.us):
>
> +plan skip_all => "disabled until after minor releases, due to instability";
Right:
https://pgdgbuild.dus.dg-i.net/view/Snapshot/job/postgresql-14-binaries-snapshot/366/architecture=s390x,distribution=sid/consoleText
-> t/031_recovery_conflict.pl ........... skipped: disabled until after minor releases, due to instability
> Now your mainframe build bot is regularly failing for whatever timing
> reason, in 16 and master. That's quite useful because your tests have
> made us or at least me a lot more confident that the fix is good (one
> of the reasons progress has been slow is that failures in CI and BF
> were pretty rare and hard to analyse). But... I wonder why it isn't
> failing for you in 15? Are you able to check if it ever has? I
> suppose we could go and do the "disabled due to instability" thing in
> 15 and 16, and then later we'll un-disable it in 16 when we back-patch
> the fix into it.
The current explanation is that builds are only running frequently for
16 and devel, and the periodic extra test jobs only run "make check"
and the postgresql-common testsuite, not the full server testsuite.
I had "snapshot" jobs configured for basically everything (server and
extensions) for some time, but ultimately realized that I don't have
the slightest time to look at everything, so I disabled them again
about 3 weeks ago. This removed enough noise so I could actually look
at the failing 16 and devel jobs again.
I don't see any failures of that kind for the 15 snapshot build while
it was still running, the failures in there are all something else
(mostly problems outside PG).
https://pgdgbuild.dus.dg-i.net/view/Snapshot/job/postgresql-15-binaries-snapshot/
I'll enable the server snapshot builds again, those shouldn't be too
noisy.
Christoph