From 87ab198b73ce774cfb15541c32bee42e963c2c9b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicki=20K=C5=99=C3=AD=C5=BEek?= Date: Wed, 2 Jul 2025 18:00:16 +0200 Subject: [PATCH] Use proper wait in rndc test Previously, the one-second sleep was unreliable, as it didn't properly indicate that the rndc reconfig has been processed. The "test 'rndc reconfig' with a broken config" check would sometimes fail under TSAN in CI, because the previous rndc reconfig was still ongoing, and the subsequent rndc reconfig was ignored. --- bin/tests/system/enginepkcs11/tests_sh_enginepkcs11.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/tests/system/enginepkcs11/tests_sh_enginepkcs11.py b/bin/tests/system/enginepkcs11/tests_sh_enginepkcs11.py index 4bad00add4..7a5ed394e6 100644 --- a/bin/tests/system/enginepkcs11/tests_sh_enginepkcs11.py +++ b/bin/tests/system/enginepkcs11/tests_sh_enginepkcs11.py @@ -51,6 +51,6 @@ pytestmark = pytest.mark.extra_artifacts( ) -@isctest.mark.flaky(max_runs=3) # GL#4605 +@isctest.mark.flaky(max_runs=5) # GL#4605 def test_enginepkcs11(run_tests_sh): run_tests_sh()