diff options
author | Bram Moolenaar <Bram@vim.org> | 2022-06-13 21:42:45 +0100 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2022-06-13 21:42:45 +0100 |
commit | 2d12c25a1b73fb6991006fd970b3132ab8ee8b62 (patch) | |
tree | 792f7cec3f4beb90fc67ab120ea87e3155c13686 /src/testdir/Makefile | |
parent | db77c49401145d76441fbb3d22a1d7d987681c13 (diff) |
patch 8.2.5084: when the GUI shows a dialog tests get stuckv8.2.5084
Problem: When the GUI shows a dialog tests get stuck.
Solution: Add the --gui-dialog-file argument.
Diffstat (limited to 'src/testdir/Makefile')
-rw-r--r-- | src/testdir/Makefile | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/testdir/Makefile b/src/testdir/Makefile index c782da9dfe..adec1f167e 100644 --- a/src/testdir/Makefile +++ b/src/testdir/Makefile @@ -89,6 +89,7 @@ clean: -rm -rf $(RM_ON_RUN) $(RM_ON_START) -rm -f valgrind.* -rm -f asan.* + -rm -f guidialog guidialogfile # Delete the files produced by benchmarking, so they can run again. benchmarkclean: @@ -127,7 +128,8 @@ tinytests: $(SCRIPTS_TINY_OUT) # New style of tests uses Vim script with assert calls. These are easier # to write and a lot easier to read and debug. # Limitation: Only works with the +eval feature. -RUN_VIMTEST = VIMRUNTIME=$(SCRIPTSOURCE) $(VALGRIND) $(VIMPROG) -f $(GUI_FLAG) -u unix.vim +# Add --gui-dialog-file to avoid getting stuck in a dialog. +RUN_VIMTEST = VIMRUNTIME=$(SCRIPTSOURCE) $(VALGRIND) $(VIMPROG) -f $(GUI_FLAG) -u unix.vim --gui-dialog-file guidialog newtests: newtestssilent @/bin/sh -c "if test -f messages; then cat messages; fi" |