From 1dddbe697e757431cc676d001e5035aa7b67540c Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Tue, 15 Jun 2021 16:53:58 +0200 Subject: tests: Speculatively stabilize history tests If we're not waiting for the async INSERT in the SQL database, it can happen that :debug-dump-history gets called before the history entry was addeded to the actual database. See #5390 --- tests/end2end/features/test_history_bdd.py | 1 + 1 file changed, 1 insertion(+) diff --git a/tests/end2end/features/test_history_bdd.py b/tests/end2end/features/test_history_bdd.py index 3a44c2c11..29958c3e6 100644 --- a/tests/end2end/features/test_history_bdd.py +++ b/tests/end2end/features/test_history_bdd.py @@ -50,6 +50,7 @@ def check_query(quteproc, name, value): @bdd.then(bdd.parsers.parse("the history should contain:\n{expected}")) def check_history(quteproc, server, tmpdir, expected): + quteproc.wait_for(message='INSERT INTO History *', category='sql') path = tmpdir / 'history' quteproc.send_cmd(':debug-dump-history "{}"'.format(path)) quteproc.wait_for(category='message', loglevel=logging.INFO, -- cgit v1.2.3-54-g00ecf