Skip to content

Commit 29891c4

Browse files
committed
patch 8.0.0145: running tests on MS-Windows is noisy
Problem: Running tests on MS-Windows is a little bit noisy. Solution: Redirect some output to "nul". (Ken Takata)
1 parent aaeabfb commit 29891c4

2 files changed

Lines changed: 9 additions & 7 deletions

File tree

src/testdir/Make_dos.mak

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -44,12 +44,12 @@ $(DOSTMP_INFILES): $(*B).in
4444
# This moves test99.in to test99.in.bak temporarily.
4545
$(TEST_OUTFILES): $(DOSTMP)\$(*B).in
4646
-@if exist test.out DEL test.out
47-
move $(*B).in $(*B).in.bak
48-
copy $(DOSTMP)\$(*B).in $(*B).in
49-
copy $(*B).ok test.ok
47+
move $(*B).in $(*B).in.bak > nul
48+
copy $(DOSTMP)\$(*B).in $(*B).in > nul
49+
copy $(*B).ok test.ok > nul
5050
$(VIMPROG) -u dos.vim $(NO_PLUGIN) -s dotest.in $(*B).in
51-
-@if exist test.out MOVE /y test.out $(DOSTMP)\$(*B).out
52-
-@if exist $(*B).in.bak move /y $(*B).in.bak $(*B).in
51+
-@if exist test.out MOVE /y test.out $(DOSTMP)\$(*B).out > nul
52+
-@if exist $(*B).in.bak move /y $(*B).in.bak $(*B).in > nul
5353
-@if exist test.ok del test.ok
5454
-@if exist Xdir1 rd /s /q Xdir1
5555
-@if exist Xfind rd /s /q Xfind
@@ -58,10 +58,10 @@ $(TEST_OUTFILES): $(DOSTMP)\$(*B).in
5858
$(VIMPROG) -u dos.vim $(NO_PLUGIN) "+set ff=unix|f test.out|wq" \
5959
$(DOSTMP)\$(*B).out
6060
@diff test.out $*.ok & if errorlevel 1 \
61-
( move /y test.out $*.failed \
61+
( move /y test.out $*.failed > nul \
6262
& del $(DOSTMP)\$(*B).out \
6363
& echo $* FAILED >> test.log ) \
64-
else ( move /y test.out $*.out )
64+
else ( move /y test.out $*.out > nul )
6565

6666
# Must run test1 first to create small.vim.
6767
# This rule must come after the one that copies the input files to dostmp to

src/version.c

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -764,6 +764,8 @@ static char *(features[]) =
764764

765765
static int included_patches[] =
766766
{ /* Add new patch number below this line */
767+
/**/
768+
145,
767769
/**/
768770
144,
769771
/**/

0 commit comments

Comments
 (0)