From e13de491391322e3d66251cc04dc7970e22c3484 Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Thu, 7 Sep 2023 11:47:42 +1200 Subject: [PATCH] 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 Reported-by: Bharath Rupireddy Discussion: https://postgr.es/m/CALj2ACVr8au2J_9D88UfRCi0JdWhyQDDxAcSVav0B0irx9nXEg%40mail.gmail.com --- src/test/recovery/t/031_recovery_conflict.pl | 1 + 1 file changed, 1 insertion(+) diff --git a/src/test/recovery/t/031_recovery_conflict.pl b/src/test/recovery/t/031_recovery_conflict.pl index 545d523edf..99f154ae10 100644 --- a/src/test/recovery/t/031_recovery_conflict.pl +++ b/src/test/recovery/t/031_recovery_conflict.pl @@ -10,6 +10,7 @@ use PostgreSQL::Test::Cluster; use PostgreSQL::Test::Utils; use Test::More; +plan skip_all => "disabled due to instability"; # Set up nodes my $node_primary = PostgreSQL::Test::Cluster->new('primary');