From bc84cf2585f2ae3a08e353f573d997586d6ecdf4 Mon Sep 17 00:00:00 2001 From: Jan Edmund Lazo Date: Thu, 26 Mar 2020 19:29:20 -0400 Subject: vim-patch:8.2.0457: Test_quotestar() often fails when run under valgrind Problem: Test_quotestar() often fails when run under valgrind. Solution: Wait longer for the GUI to start. https://github.com/vim/vim/commit/26bde6e2eb307898ab7ed42bf8e7e2ccde979e02 --- src/nvim/testdir/test_quotestar.vim | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src') diff --git a/src/nvim/testdir/test_quotestar.vim b/src/nvim/testdir/test_quotestar.vim index ce5a9ee827..77a5153a81 100644 --- a/src/nvim/testdir/test_quotestar.vim +++ b/src/nvim/testdir/test_quotestar.vim @@ -108,7 +108,8 @@ func Do_test_quotestar_for_x11() call remote_send(name, ":gui -f\") endif " Wait for the server in the GUI to be up and answering requests. - call WaitForAssert({-> assert_match("1", remote_expr(name, "has('gui_running')", "", 1))}) + " On some systems and with valgrind this can be very slow. + call WaitForAssert({-> assert_match("1", remote_expr(name, "has('gui_running')", "", 1))}, 10000) call remote_send(name, ":let @* = 'maybe'\") call WaitForAssert({-> assert_equal("maybe", remote_expr(name, "@*", "", 2))}) -- cgit