Skip to content

Commit 5881828

Browse files
ychinchrisbra
authored andcommitted
ci: syntax tests spam output
Currently syntax tests outputs all the Vim commands to the console, which is annoying for a local developer but also makes the CI output impossible to parse and just printing all the terminal output comes with a performance penalty. So let's just simply redirect all output to /dev/null similar to what the script tests do. This can be turned off locally for someone diagnosing issues but it should not be the default behavior to output all terminal control sequences to output in CI. closes: #16612 Signed-off-by: Yee Cheng Chin <[email protected]> Signed-off-by: Christian Brabandt <[email protected]>
1 parent 8cc725e commit 5881828

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

runtime/syntax/Makefile

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,12 @@ RUN_VIMTEST = VIMRUNTIME=$(VIMRUNTIME) $(VALGRIND) $(ENVVARS) ../$(VIMPROG) -f $
2626
# If a test succeeds a testdir/done/{name} file will be written.
2727
# If a test fails a testdir/failed/{name}.dump file will be written.
2828
# Progress and error messages can be found in "testdir/messages".
29+
# Comment out the "> /dev/null" part to see the in-progress Vim behaviors.
2930
test:
3031
@# the "vimcmd" file is used by the screendump utils
3132
@echo "../$(VIMPROG)" > testdir/vimcmd
3233
@echo "$(RUN_VIMTEST)" >> testdir/vimcmd
33-
VIMRUNTIME=$(VIMRUNTIME) $(ENVVARS) $(VIMPROG) --clean --not-a-term $(DEBUGLOG) -u testdir/runtest.vim
34+
VIMRUNTIME=$(VIMRUNTIME) $(ENVVARS) $(VIMPROG) --clean --not-a-term $(DEBUGLOG) -u testdir/runtest.vim > /dev/null
3435
@rm -f testdir/Xfilter
3536
@# FIXME: Temporarily show the whole file to find out what goes wrong
3637
@#if [ -f testdir/messages ]; then tail -n 6 testdir/messages; fi

0 commit comments

Comments
 (0)