From 057ce115de119a4973dd68b4844884896478ecb0 Mon Sep 17 00:00:00 2001 From: "Alex Chi Z." <4198311+skyzh@users.noreply.github.com> Date: Mon, 14 Apr 2025 10:51:17 -0400 Subject: [PATCH] fix(test): allow stale generation errors (1/2) (#11531) ## Problem Part of https://github.com/neondatabase/neon/issues/11486 ## Summary of changes 50% of the test instability of `test_create_churn_during_restart` are due to error message gets changed. Allow the new error message. Still need to fix other errors due to failure to acquire semaphore in this or the next patch. Signed-off-by: Alex Chi Z --- test_runner/regress/test_tenants.py | 1 + 1 file changed, 1 insertion(+) diff --git a/test_runner/regress/test_tenants.py b/test_runner/regress/test_tenants.py index c613a79374..c00f8f4ca5 100644 --- a/test_runner/regress/test_tenants.py +++ b/test_runner/regress/test_tenants.py @@ -390,6 +390,7 @@ def test_create_churn_during_restart(neon_env_builder: NeonEnvBuilder): # Tenant creation requests which arrive out of order will generate complaints about # generation nubmers out of order. env.pageserver.allowed_errors.append(".*Generation .+ is less than existing .+") + env.pageserver.allowed_errors.append(".*due to stale generation.+") # Timeline::flush_and_shutdown cannot tell if it is hitting a failure because of # an incomplete attach, or some other problem. In the field this should be rare,