<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=""><div class="">Two questions:</div><div class=""><br class=""></div><div class="">1) Has anyone thought about adding a new “make check” configuration / envvar that enables more verbosity, which CI would enable but normal humans haven’t? The CI configs could be set to dump the whole file.</div><div class=""><br class=""></div><div class="">2) Instead of dumping the entire input by default, would it be reasonable to change the default “make check” to have FileCheck print the 10 lines before and after the mismatch? Most problems are close by the check failure. If you want to check extra fancy, dump the CHECK-LABEL region.</div><div class=""><br class=""></div><div class="">The combination of both seem like significant usability improvements for both CI and humans.</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""></div><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 18, 2020, at 10:43 AM, Joel E. Denny via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">As for the ordering issue... from the command line, I tend to set verbosity high, and so I pipe to a pager and search for "error:". I prefer errors before the input dump then. My point is that it should be configurable if we change the default ordering.<br class=""></div><div class=""><br class=""></div><div class="">Joel<br class=""></div><div class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 18, 2020 at 1:13 PM Joel E. Denny <<a href="mailto:jdenny.ornl@gmail.com" class="">jdenny.ornl@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div dir="ltr" class=""><div class=""></div><div class=""></div><div class="">Thanks for bringing this discussion to the list so we can see a broader set of opinions on what the default should be.</div><div class=""><br class=""></div><div class="">I like Johannes's suggestion that defaults should consider the new LLVM user. For that case, I think verbosity should be low, and diagnostics should mention how to increase verbosity.<br class=""></div><div class=""><br class=""></div><div class="">For CI, I agree verbosity should be high because it's not easy for many LLVM contributors to try again with higher verbosity.<br class=""></div><div class=""><br class=""></div><div class="">For my personal usage, I don't care what the default behavior is as long as behavior is easy to customize. FILECHECK_OPTS lets me do that per test suite run, or in my ~/.profile, or in my CI configs, etc.<br class=""></div><div class=""><br class=""></div><div class="">Joel<br class=""></div><div class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 18, 2020 at 12:45 PM Sjoerd Meijer via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
I would guess that in a CI system the order doesn't matter much because you look at a webpage? I looked at some build bots today/yesterday that now also show this, and yeah, it's fine either way, I was guessing.<br class="">
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
My primary use-case is usage in a terminal, and displaying the errors first followed by all input makes this pretty unusable.<br class="">
</div>
<div id="gmail-m_7993811440804990612gmail-m_-5473924934954905795appendonsend" class=""></div>
<hr style="display:inline-block;width:98%" class="">
<div id="gmail-m_7993811440804990612gmail-m_-5473924934954905795divRplyFwdMsg" dir="ltr" class=""><font style="font-size:11pt" face="Calibri, sans-serif" class=""><b class="">From:</b> Chris Tetreault <<a href="mailto:ctetreau@quicinc.com" target="_blank" class="">ctetreau@quicinc.com</a>><br class="">
<b class="">Sent:</b> 18 June 2020 17:34<br class="">
<b class="">To:</b> Sjoerd Meijer <<a href="mailto:Sjoerd.Meijer@arm.com" target="_blank" class="">Sjoerd.Meijer@arm.com</a>><br class="">
<b class="">Cc:</b> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a> <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>><br class="">
<b class="">Subject:</b> RE: [llvm-dev] FileCheck</font>
<div class=""> </div>
</div>
<div lang="EN-US" class="">
<div class=""><p class="">For anybody viewing these failures through some sort of CI system, showing the error first then the input file is more useful for the same reasons you mentioned. Personally, I rarely run filecheck by hand from the command prompt, so your
change would make my life worse. Granted, I’m just one person.</p><div class=""> <br class="webkit-block-placeholder"></div><p class="">The point I’m trying to make is that I don’t think it’s clear-cut which order is better, so maybe we shouldn’t change it. I think it might be fine to add an option to swap the order, but I’d be very sad if it started dumping to some random
file by default.</p><div class=""> <br class="webkit-block-placeholder"></div><p class="">Thanks,</p><p class=""> Christopher Tetreault</p><div class=""> <br class="webkit-block-placeholder"></div>
<div class="">
<div style="border-color:rgb(225,225,225) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in" class=""><p class=""><b class="">From:</b> llvm-dev <<a href="mailto:llvm-dev-bounces@lists.llvm.org" target="_blank" class="">llvm-dev-bounces@lists.llvm.org</a>> <b class="">
On Behalf Of </b>Sjoerd Meijer via llvm-dev<br class="">
<b class="">Sent:</b> Thursday, June 18, 2020 9:16 AM<br class="">
<b class="">To:</b> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class="">
<b class="">Subject:</b> [EXT] [llvm-dev] FileCheck</p>
</div>
</div><div class=""> <br class="webkit-block-placeholder"></div>
<div class=""><p class=""><span style="font-size: 12pt;" class="">Hello,</span></p>
</div>
<div class=""><div class=""><span style="font-size: 12pt;" class=""> </span><br class="webkit-block-placeholder"></div>
</div>
<div class=""><p class=""><span style="font-size: 12pt;" class="">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.
</span></p>
</div>
<div class=""><div class=""><span style="font-size: 12pt;" class=""> </span><br class="webkit-block-placeholder"></div>
</div>
<div class=""><p class=""><span style="font-size: 12pt;" class="">I do see some advantages of dumping the input to FileCheck, but an improvement for me would be:</span></p>
</div>
<div class="">
<ul type="disc" class="">
<li style="" class=""><span style="font-size:12pt" class="">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.</span></li><li style="" class=""><span style="font-size:12pt" class="">dump it to a separate file (controlled with an option).</span></li></ul>
</div>
<div class=""><p class=""><span style="font-size: 12pt;" class="">I am interested in changing the behaviour, because I think I find setting environment varibale "FILECHECK_OPTS="--dump-input never"" inconvenient. </span></p>
</div>
<div class=""><div class=""><span style="font-size: 12pt;" class=""> </span><br class="webkit-block-placeholder"></div>
</div>
<div class=""><p class=""><span style="font-size: 12pt;" class="">My 2 pennies.</span></p>
</div>
<div class=""><p class=""><span style="font-size: 12pt;" class="">Sjoerd.</span></p>
</div>
</div>
</div>
</div>
_______________________________________________<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="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">
</blockquote></div></div>
</blockquote></div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></body></html>