<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><a href="https://reviews.llvm.org/D49328" class="">https://reviews.llvm.org/D49328</a><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 13, 2018, at 9:16 AM, David Blaikie <dblaikie@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Could be useful - as Paul mentioned, having it on standard output could be good - especially for buildbots (where rerunning the command is impractical). Though a more generalized solution for 'lit' where it dumps all the inputs and outputs (well, I guess, the textually representable ones - maybe that's basically just FileCheck) in a way that buildbot could split them out into separate files (easier to read, download/use, etc than one big stream), would be extra super awesome.<br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Thu, Jul 12, 2018 at 6:31 PM George Karpenkov via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br class="">
<br class="">
FileCheck is a great tool for writing tests.<br class="">
However, it can be also a great tool for hiding the error cause from you, especially if a very common idiom<br class="">
<br class="">
RUN: ./myprog | FileCheck %s<br class="">
<br class="">
is used.<br class="">
If you need to know the output of “myprog” to figure out why your test is failing — then well, good luck,<br class="">
you would need to manually copy’n paste that line, run it, and then note the output.<br class="">
(produced line “expected/got” are rarely enough to debug the problem)<br class="">
<br class="">
Would it be useful to have an optional, off-by-default mode for FileCheck, turned on by an environment variable,<br class="">
which would save all the input it gets, and then dump it on failure?<br class="">
I also wish we could get a <br class="">
<br class="">
The test case I imagine would be to run:<br class="">
<br class="">
ninja check-X<br class="">
<br class="">
note the failure,<br class="">
and then rerun:<br class="">
<br class="">
env FILECHECK_SUPER_VERBOSE=1 ninja check-X<br class="">
<br class="">
Thoughts?<br class="">
George<br class="">
_______________________________________________<br class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class="">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">
</blockquote></div></div>
</div></blockquote></div><br class=""></body></html>