Boost C++ Libraries: Ticket #5959: Getting a full test log (log-level=all) depends on the argument order https://svn.boost.org/trac10/ticket/5959 <p> When using Boost.Test it depends on the argument order if I can get a full test log or not. log-level is set to "all" in both cases, but note the changed argument order. </p> <blockquote> <p> test --report_level=no --output_format=XML --log-level=all <em>(test log only for failing tests)</em> </p> </blockquote> <blockquote> <p> test --log_level=all --output_format=XML --report_level=no <em>(works - full test log)</em> </p> </blockquote> <p> Noticed when using 1.40.0 but reproduced with trunk. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/5959 Trac 1.4.3 anonymous Wed, 28 Sep 2011 19:16:42 GMT <link>https://svn.boost.org/trac10/ticket/5959#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/5959#comment:1</guid> <description> <p> I just realized, it was not the wrong argument order, but using the argument "log-level" (dash) instead of log_level (underscore). </p> <p> I`m embarrassed. </p> <p> Sorry. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Gennadiy Rozental</dc:creator> <pubDate>Mon, 17 Oct 2011 02:30:56 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/5959#comment:2 https://svn.boost.org/trac10/ticket/5959#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> Ticket