pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Disable 031_recovery_conflict.pl in 15 and 16.
2+ messages / 1 participants
[nested] [flat]

* pgsql: Disable 031_recovery_conflict.pl in 15 and 16.
@ 2023-09-06 23:50  Thomas Munro <tmunro@postgresql.org>
  0 siblings, 0 replies; 2+ messages in thread

From: Thomas Munro @ 2023-09-06 23:50 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Disable 031_recovery_conflict.pl in 15 and 16.

This test fails due to known bugs in the test and the server.  Those
will be fixed in master shortly and possibly back-patched a bit later,
but in the meantime it is unhelpful for package maintainers if the tests
randomly fail, and it's not a good time to make complex changes in 16.

This had already been done for older branches prior to 15's release.
Now we're about to release 16, and Debian's test builds are regularly
failing on one architecture, so let's do the same for 15 and 16.

Reported-by: Christoph Berg <myon@debian.org>
Reported-by: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Discussion: https://postgr.es/m/CALj2ACVr8au2J_9D88UfRCi0JdWhyQDDxAcSVav0B0irx9nXEg%40mail.gmail.com

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/8d1cf9674a253f88d52c365804b9b4d3a7eeab9d

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 1 +
1 file changed, 1 insertion(+)



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* pgsql: Disable 031_recovery_conflict.pl in 15 and 16.
@ 2023-09-06 23:50  Thomas Munro <tmunro@postgresql.org>
  0 siblings, 0 replies; 2+ messages in thread

From: Thomas Munro @ 2023-09-06 23:50 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Disable 031_recovery_conflict.pl in 15 and 16.

This test fails due to known bugs in the test and the server.  Those
will be fixed in master shortly and possibly back-patched a bit later,
but in the meantime it is unhelpful for package maintainers if the tests
randomly fail, and it's not a good time to make complex changes in 16.

This had already been done for older branches prior to 15's release.
Now we're about to release 16, and Debian's test builds are regularly
failing on one architecture, so let's do the same for 15 and 16.

Reported-by: Christoph Berg <myon@debian.org>
Reported-by: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Discussion: https://postgr.es/m/CALj2ACVr8au2J_9D88UfRCi0JdWhyQDDxAcSVav0B0irx9nXEg%40mail.gmail.com

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/e13de491391322e3d66251cc04dc7970e22c3484

Modified Files
--------------
src/test/recovery/t/031_recovery_conflict.pl | 1 +
1 file changed, 1 insertion(+)



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2023-09-06 23:50 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-09-06 23:50 pgsql: Disable 031_recovery_conflict.pl in 15 and 16. Thomas Munro <tmunro@postgresql.org>
2023-09-06 23:50 pgsql: Disable 031_recovery_conflict.pl in 15 and 16. Thomas Munro <tmunro@postgresql.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox