From 768c8d9972b7064b6e50b7d421506b76b6074221 Mon Sep 17 00:00:00 2001 From: Joonas Koivunen Date: Thu, 16 Mar 2023 11:03:21 +0200 Subject: [PATCH] test: allow gc to get unlucky (#3826) this failure case was probably introduced by b220ba6, because earlier the gc would always have run fast enough for restart every 1s. however, test got added later, so we have just been lucky. fixes #3824 by allowing this error to happen. --- .../regress/test_pageserver_restarts_under_workload.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/test_runner/regress/test_pageserver_restarts_under_workload.py b/test_runner/regress/test_pageserver_restarts_under_workload.py index 28159778fe..eab8b112f0 100644 --- a/test_runner/regress/test_pageserver_restarts_under_workload.py +++ b/test_runner/regress/test_pageserver_restarts_under_workload.py @@ -17,6 +17,12 @@ def test_pageserver_restarts_under_worload(neon_simple_env: NeonEnv, pg_bin: PgB n_restarts = 10 scale = 10 + # the background task may complete the init task delay after finding an + # active tenant, but shutdown starts right before Tenant::gc_iteration + env.pageserver.allowed_errors.append( + r".*Gc failed, retrying in \S+: Cannot run GC iteration on inactive tenant" + ) + def run_pgbench(pg: Postgres): connstr = pg.connstr() log.info(f"Start a pgbench workload on pg {connstr}")