Boost logo

Boost :

From: pbristow_at_[hidden]
Date: 2019-11-07 09:51:18


> -----Original Message-----
> From: Boost <boost-bounces_at_[hidden]> On Behalf Of Raffi Enficiaud via
> Boost
> Sent: 7 November 2019 06:47
> To: boost_at_[hidden]
> Cc: Raffi Enficiaud <raffi.enficiaud_at_[hidden]>
> Subject: Re: [boost] [1.72][Test][Math][Fiber] Recent breaking change in Boost.Test
> breaks fiber/math tests
>
> On 06.11.19 10:49, Paul A Bristow via Boost wrote:
> > There are times when eminently sensible suggestions (like yours and
> > mine) are not the best thing to do.
> >
> > I agree that the benefit isn't worth causing downstream trouble.
> >
> > But I would still like some warning in the documentation. I've
> > written
> > notes-to-self:
>
> I am all for helping you there. My question is: where should I put this warning? It is
> not clear to me if you expect this warning in the doc, and if so, which section of
> the doc.

https://www.boost.org/doc/libs/1_71_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/log_level.html

Doesn't make clear to me what the default level is 'out of the box'? And perhaps warn on other page that it isn't output at the default log level.

https://www.boost.org/doc/libs/1_71_0/libs/test/doc/html/boost_test/utf_reference/testout_reference/test_output_macro_message.html

should also suggest that running with --log_level="message2 is required to get this to actually output anything.

https://www.boost.org/doc/libs/1_71_0/libs/test/doc/html/boost_test/test_output/test_tools_support_for_logging/test_output_macro_message.html

and this too.

(I am ashamed to report that I did not follow my own injunction to use hyperlinks to get to this page ☹ As they say, "you can lead a horse to water, but you can't make him drink").

I also didn't find that #define BOOST_TEST_LOG_LEVEL message ort "message" had the desired effect.
Many people might expect this (and consider it desirable to force the messages out.

Thanks

HTH

Paul


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk