From a50a7e8ac083285222fa5923e25991eaeee62885 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Fri, 18 Nov 2022 16:56:27 +0200 Subject: [PATCH] Try to silence test_gc_cutoff flakiness. Commit d013a2b227 changed the test, so that it fails if pgbench runs to completion without triggering the failpoint. That has now happened several times in the CI. That's not expected, so this needs some investigation, but as a quick fix just make the pgbench runs longer so that we're closer to the situation before commit d013a2b227. See https://github.com/neondatabase/neon/issues/2856 --- test_runner/regress/test_gc_cutoff.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test_runner/regress/test_gc_cutoff.py b/test_runner/regress/test_gc_cutoff.py index f760c993f4..9c9b9d26c7 100644 --- a/test_runner/regress/test_gc_cutoff.py +++ b/test_runner/regress/test_gc_cutoff.py @@ -38,7 +38,7 @@ def test_gc_cutoff(neon_env_builder: NeonEnvBuilder, pg_bin: PgBin): for _ in range(5): with pytest.raises(Exception): - pg_bin.run_capture(["pgbench", "-N", "-c5", "-T100", "-Mprepared", connstr]) + pg_bin.run_capture(["pgbench", "-N", "-c5", "-T200", "-Mprepared", connstr]) env.pageserver.stop() env.pageserver.start() pageserver_http.configure_failpoints(("after-timeline-gc-removed-layers", "exit"))