From 684329d4d259fc947124522c2a2a7eb34bd1c226 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Sat, 19 Nov 2022 19:28:56 +0200 Subject: [PATCH] Another attempt at silencing test_gc_cutoff failures. Increse the pgbench runtimes even further. The theory is that when there are many other tests running at the same time, one pgbench run could take a long time until it generates enough layers for GC to kick in. --- test_runner/regress/test_gc_cutoff.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/test_runner/regress/test_gc_cutoff.py b/test_runner/regress/test_gc_cutoff.py index 5899102586..1b98a414da 100644 --- a/test_runner/regress/test_gc_cutoff.py +++ b/test_runner/regress/test_gc_cutoff.py @@ -8,6 +8,7 @@ from fixtures.neon_fixtures import NeonEnvBuilder, PgBin # normally restarts after it. Also, there should be GC ERRORs in the log, # but the fixture checks the log for any unexpected ERRORs after every # test anyway, so it doesn't need any special attention here. +@pytest.mark.timeout(600) def test_gc_cutoff(neon_env_builder: NeonEnvBuilder, pg_bin: PgBin): env = neon_env_builder.init_start() @@ -38,7 +39,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", "-P1", "-N", "-c5", "-T200", "-Mprepared", connstr]) + pg_bin.run_capture(["pgbench", "-P1", "-N", "-c5", "-T500", "-Mprepared", connstr]) env.pageserver.stop() env.pageserver.start() pageserver_http.configure_failpoints(("after-timeline-gc-removed-layers", "exit"))