[llvm-dev] FileCheck

[Matt Arsenault via llvm-dev]

> On Jun 18, 2020, at 12:15, Sjoerd Meijer via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 
> Hello,
> 
> I am not sold on FileCheck's new behaviour. For failing tests in verbose mode, it first dump the actual error messages, followed by the annotated input file to FileCheck. The result is I can't immediately see error messages if the input is more than just a few lines long, so I have to scroll all the way up to see the errors, then down again, etc. 
> 
> I do see some advantages of dumping the input to FileCheck, but an improvement for me would be:
> to dump the input first, then followed by the error message, so that I can the errors first, and then decide to scroll up if I am interested to do so.
> dump it to a separate file (controlled with an option).
> I am interested in changing the behaviour, because I think I find setting environment varibale "FILECHECK_OPTS="--dump-input never"" inconvenient. 
> 
> My 2 pennies.
> Sjoerd.
> _______________________________________________


+1. The new behavior makes sense if you break 1 test with 100 lines of output. It stops making sense if you break 20 tests with 1000s of lines of output. Some more aggressive dumping by default on buildbots may make sense

-Matt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200618/767ff640/attachment.html>