diff --git a/src/bin/pg_combinebackup/t/011_ib_truncation.pl b/src/bin/pg_combinebackup/t/011_ib_truncation.pl
index 47d84434452..f9182ef668a 100644
--- a/src/bin/pg_combinebackup/t/011_ib_truncation.pl
+++ b/src/bin/pg_combinebackup/t/011_ib_truncation.pl
@@ -23,7 +23,8 @@ my $full_backup = "$backup_path/full";
 # test will only find the issue when run with a small RELSEG_SIZE. As of this
 # writing, one of the CI runs is configured using --with-segsize-blocks=6, and
 # we aim to have this test check for the issue only in that configuration.
-my $target_blocks = 6;
+
+my $target_blocks = 131072; # RELSEG_SIZE from pg_config.h
 my $block_size = $primary->safe_psql('postgres',
 	"SELECT current_setting('block_size')::int;");
 
@@ -87,15 +88,13 @@ $primary->backup('incr',
 # the INCREMENTAL file header contained an incorrect truncation_block value.
 my $restored = PostgreSQL::Test::Cluster->new('node2');
 $restored->init_from_backup($primary, 'incr', combine_with_prior => ['full']);
-$restored->start();
 
-# Check that the restored table contains the correct number of rows
-my $restored_count =
-  $restored->safe_psql('postgres', "SELECT count(*) FROM t;");
-is($restored_count, $rows_after_truncation,
-	'Restored backup has correct row count');
+#
+# DEBUG: Force these tests to fail to preserve the cluster and backup state for
+# debugging purposes.
+#
+is(1, 0, 'DEBUG: make it fail');
 
 $primary->stop;
-$restored->stop;
 
 done_testing();