changeset 24178:d5328b2b0edf v8.2.2630

patch 8.2.2630: hard to see where a test gets stuck Commit: https://github.com/vim/vim/commit/592f57f5fec1064cc276a0d7992cc543bed04fd5 Author: Bram Moolenaar <Bram@vim.org> Date: Sat Mar 20 16:44:25 2021 +0100 patch 8.2.2630: hard to see where a test gets stuck Problem: Hard to see where a test gets stuck. Solution: Print the executed test function. (Dominique Pell?, closes https://github.com/vim/vim/issues/7975)
author Bram Moolenaar <Bram@vim.org>
date Sat, 20 Mar 2021 16:45:02 +0100
parents db3a2032bfac
children 62b22d6b2251
files src/testdir/Makefile src/version.c
diffstat 2 files changed, 3 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/src/testdir/Makefile
+++ b/src/testdir/Makefile
@@ -12,7 +12,7 @@ SCRIPTSOURCE = ../../runtime
 # Comment out this line to see the verbose output of tests.
 #
 # Catches SwapExists to avoid hanging at the ATTENTION prompt.
-REDIR_TEST_TO_NULL = --cmd 'au SwapExists * let v:swapchoice = "e"' > /dev/null
+REDIR_TEST_TO_NULL = --cmd 'au SwapExists * let v:swapchoice = "e"' | LC_ALL=C LANG=C LANGUAGE=C awk '/Executing Test_/{match($$0, "Executing Test_[^\\)]*\\)"); print substr($$0, RSTART, RLENGTH) "\r"; fflush()}'
 
 # Uncomment this line to use valgrind for memory leaks and extra warnings.
 #   The output goes into a file "valgrind.testN"
--- a/src/version.c
+++ b/src/version.c
@@ -751,6 +751,8 @@ static char *(features[]) =
 static int included_patches[] =
 {   /* Add new patch number below this line */
 /**/
+    2630,
+/**/
     2629,
 /**/
     2628,