
We just upgraded from 1.29.0 to 1.30.0 and started having a problem running in the unit test framework. When we start the test with the command line parameter "--report_level=detailed" the tests crash. They work fine if we set the environment parameter BOOST_TEST_REPORT_LEVEL=detailed, or when we set other command line parameters, such as "--log_level=detailed". I looked at the code in libs/test/src/unit_test_main.cpp and saw that the command line parsing for report_level doesn't occur until after the unit test suite has been invoked. It appears that the unit test is then getting a command line that contains "--report_level=detailed". In our case, it doesn't know what to do with this. I hacked our copy of unit_test_main.cpp to parse the command line for --report_level before starting the unit test suite, storing the value locally. Has anyone else had this problem? Are we using the unit test framework the wrong way? Do you think I fixed it the right way, and will there be an official fix soon? Thanks, -John Van Horne

I looked at the code in libs/test/src/unit_test_main.cpp and saw that the command line parsing for report_level doesn't occur until after the unit test suite has been invoked. It appears that the unit test is then getting a command line that contains "--report_level=detailed". In our case, it doesn't know what to do with this.
Sorry. My fault. Next release will contain completely reworked version of CLA processing. It won't have this issue also. Gennadiy.

We just upgraded from 1.29.0 to 1.30.0 and started having a problem running in the unit test framework. When we start the test with the command line parameter "--report_level=detailed" the tests crash. They work fine if we set the environment parameter BOOST_TEST_REPORT_LEVEL=detailed, or when we set other command line parameters, such as "--log_level=detailed".
I looked at the code in libs/test/src/unit_test_main.cpp and saw that the command line parsing for report_level doesn't occur until after the unit test suite has been invoked. It appears that the unit test is then getting a command line that contains "--report_level=detailed". In our case, it doesn't know what to do with this.
If that's correct it's very bad indeed - all the type_traits regression tests rely on --report-level=detailed working correctly. However I'm not seeing the online regression test results exhibiting this problem (could be that they just haven't needed rebuilding yet) - what compiler/platform are you using? Thanks, John.

If that's correct it's very bad indeed - all the type_traits regression tests rely on --report-level=detailed working correctly. However I'm not seeing the online regression test results exhibiting this problem (could be that they just haven't needed rebuilding yet) - what compiler/platform are you using?
Thanks,
John.
It's not that Boost.Test crash when this option in use. Boost.Test presumed to exclude all Boost.Test specific options from command line *before* forwarding argc/argv to the init function. It did not happend with report level. And John's application could not cope with it. Gennadiy.
participants (3)
-
Gennadiy E. Rozental
-
John Maddock
-
John Van Horne