From 2b91f507a8860b07555fedda5af493ab44dd2230 Mon Sep 17 00:00:00 2001 From: Arseny Sher Date: Sun, 17 Sep 2023 07:21:34 +0300 Subject: [PATCH] Make test_pageserver_http_get_wal_receiver_success not wait for keepalive. --- test_runner/regress/test_pageserver_api.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test_runner/regress/test_pageserver_api.py b/test_runner/regress/test_pageserver_api.py index f5bcfd52f9f2..2d837881937a 100644 --- a/test_runner/regress/test_pageserver_api.py +++ b/test_runner/regress/test_pageserver_api.py @@ -157,6 +157,8 @@ def test_pageserver_http_get_wal_receiver_success(neon_simple_env: NeonEnv): tenant_id, timeline_id = env.neon_cli.create_tenant() endpoint = env.endpoints.create_start(DEFAULT_BRANCH_NAME, tenant_id=tenant_id) + # insert something to force sk -> ps message + endpoint.safe_psql("CREATE TABLE t(key int primary key, value text)") # Wait to make sure that we get a latest WAL receiver data. # We need to wait here because it's possible that we don't have access to # the latest WAL yet, when the `timeline_detail` API is first called. @@ -168,7 +170,7 @@ def test_pageserver_http_get_wal_receiver_success(neon_simple_env: NeonEnv): ) # Make a DB modification then expect getting a new WAL receiver's data. - endpoint.safe_psql("CREATE TABLE t(key int primary key, value text)") + endpoint.safe_psql("INSERT INTO t VALUES (1, 'hey')") wait_until( number_of_iterations=5, interval=1,