adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

patch 8.2.2630: hard to see where a test gets stuck

Browse Source 
Problem:    Hard to see where a test gets stuck.
Solution:   Print the executed test function. (Dominique Pellé, closes #7975)
This commit is contained in:
Bram Moolenaar
2021-03-20 16:44:25 +01:00
parent a0399efa72
commit 592f57f5fe
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/testdir/Makefile
View File

@ -12,7 +12,7 @@ SCRIPTSOURCE = ../../runtime
# Comment out this line to see the verbose output of tests. # Comment out this line to see the verbose output of tests.
# #
# Catches SwapExists to avoid hanging at the ATTENTION prompt. # 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. # Uncomment this line to use valgrind for memory leaks and extra warnings.
# The output goes into a file "valgrind.testN" # The output goes into a file "valgrind.testN"

2
src/version.c
View File

@ -750,6 +750,8 @@ static char *(features[]) =
static int included_patches[] = static int included_patches[] =
{ /* Add new patch number below this line */ { /* Add new patch number below this line */
/**/
2630,
/**/ /**/
2629, 2629,
/**/ /**/