ci: syntax tests spam output

Commit: 
https://github.com/vim/vim/commit/58818281045fab3ab5b08f76c5745a0f71ba5ba2
Author: Yee Cheng Chin <ychin....@gmail.com>
Date:   Tue Feb 11 20:16:11 2025 +0100

    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 <ychin....@gmail.com>
    Signed-off-by: Christian Brabandt <c...@256bit.org>

diff --git a/runtime/syntax/Makefile b/runtime/syntax/Makefile
index cbea54ac3..84d6f83de 100644
--- a/runtime/syntax/Makefile
+++ b/runtime/syntax/Makefile
@@ -26,11 +26,12 @@ RUN_VIMTEST = VIMRUNTIME=$(VIMRUNTIME) $(VALGRIND) 
$(ENVVARS) ../$(VIMPROG) -f $
 # If a test succeeds a testdir/done/{name} file will be written.
 # If a test fails a testdir/failed/{name}.dump file will be written.
 # Progress and error messages can be found in "testdir/messages".
+# Comment out the "> /dev/null" part to see the in-progress Vim behaviors.
 test:
        @# the "vimcmd" file is used by the screendump utils
        @echo "../$(VIMPROG)" > testdir/vimcmd
        @echo "$(RUN_VIMTEST)" >> testdir/vimcmd
-       VIMRUNTIME=$(VIMRUNTIME) $(ENVVARS) $(VIMPROG) --clean --not-a-term 
$(DEBUGLOG) -u testdir/runtest.vim
+       VIMRUNTIME=$(VIMRUNTIME) $(ENVVARS) $(VIMPROG) --clean --not-a-term 
$(DEBUGLOG) -u testdir/runtest.vim > /dev/null 
        @rm -f testdir/Xfilter
        @# FIXME: Temporarily show the whole file to find out what goes wrong
        @#if [ -f testdir/messages ]; then tail -n 6 testdir/messages; fi

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/vim_dev/E1thvxL-00389m-5x%40256bit.org.

Raspunde prin e-mail lui