Dominique wrote:
> CI config "linux (huge, gcc, testgui, true)" is often failing > with timeout. The last information in log is: > > === > VIMRUNTIME=../../runtime ../vim -f -g -u unix.vim -U NONE --noplugin > --not-a-term -S runtest.vim test_terminal2.vim --cmd 'au SwapExists * > let v:swapchoice = "e"' > /dev/null > Error: The action has timed out. > === > > Should we comment out the following line in src/testdir/Makefile > to figure out where it hangs? > > REDIR_TEST_TO_NULL = --cmd 'au SwapExists * let v:swapchoice = "e"' > > /dev/null > > Or perhaps that line should redirect to a temporary file, > which could be shown in CI when the test fails, but not > shown when it succeeds, so it generally does not bloat logs. > > Code coverage is also unstable, possibly as a result of failing CI. I don't expect much from not doing the redirect. I have been thinking of writing a line to a file just before calling a Test_ function, and displaying this file when the test fails. After a timeout this might be tricky though, the whole script might be aborted. Perhaps there is a way to always display the file after a short while. We could split test_terminal2 like it was done before, or move a couple of tests to test_terminnal3. But even better would be if someone can reproduce the problem. I've had some success by running tests under valgrind (to simulate slow execution). -- "Hit any key to continue" is a lie. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/202101171252.10HCqAFT574462%40masaka.moolenaar.net.
