On Mon, Dec 8, 2008 at 9:47 PM, Philip Lowman <span dir="ltr"><<a href="mailto:philip@yhbt.com">philip@yhbt.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, Dec 8, 2008 at 8:14 PM, Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a>></span> wrote:<br></div><div class="gmail_quote">
<br><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
However, all that said, I suppose an option to output on failure would not be so bad as long as it is not the default.</blockquote></div><div></div></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><br>All things being equal, I actually think output on failure probably would have been a better default for most users with the current behavior of CTest being achieved through some kind of "--summarize" flag. Of course my opinion is coming as a C++ developer where if a "unit test" fails within CxxTest we're dealing with perhaps 15 lines of output. Obviously CTest does more than just unit tests. When you test CMake within CTest I can imagine some of the more complicated tests like bootstrap could be closer to 1500 lines of output (wouldn't want that one to fail) =)</div>
</div></blockquote><div><br>And yes, I agree with output on error not being the default.<br></div></div><br>-- <br>Philip Lowman<br>