Boost C++ Libraries: Ticket #13024: Using function as data source in BOOST_DATA_TEST_CASE initiate the conflict with static variables initialization

Raffi Enficiaud — Mon, 15 May 2017 10:11:04 GMT

This is quite a big change in the way the initialization of the boost.test framework works, but I agree that this is a nice feature to have. I am leaving this open for the moment.

type changed

Raffi Enficiaud — Tue, 29 Aug 2017 21:41:41 GMT

type Bugs → Feature Requests

Tue, 03 Oct 2017 10:07:24 GMT

I have faced with similar issue when upgrading to 1.65.1 and I can only say that at the moment BOOST_DATA_TEST_CASE cannot be used with something like get_files() for gettign different input files.

Could you update the manual to state that dataset is being initialized during initialization of statics?
Can you provide the estimated time when this issue be resolved? I don't want to migrate to another test framework, but now it blocks me.

Raffi Enficiaud — Thu, 28 Dec 2017 19:34:40 GMT

To unblock you, you can always mimic the dataset behaviour by manually registering test cases in the init of the test framework:

http://www.boost.org/doc/libs/release/libs/test/doc/html/boost_test/adv_scenarios/test_module_init_overview.html for test initialization function
http://www.boost.org/doc/libs/release/libs/test/doc/html/boost_test/tests_organization/test_cases/test_organization_nullary.html#ref_BOOST_TEST_CASE for manual registration

You may for instance collect the files and then manually register a test for each of them.

Raffi Enficiaud — Wed, 03 Jan 2018 00:42:42 GMT

I am not sure the crashes you are experiencing is due to a change in Boost.Test between 1.63 and a later version. The get_files function is always evaluated at static initialization time as the BOOST_DATA_TEST_CASE creates a static global object.

I tend to think that there is something in filesystem that prevents from calling functions during this global static initialization phase. So I suggest that you ask or raise a ticket on boost.filesystem side to make it clear.

However, there is the ticket #12953 that should help as it postpones the evaluation of the datasets, it would be good if you can give a try. To support this further, I suggest getting the files later in the init phase by providing a proper dataset interface to the function retrieving the files, as shown here (for instance getting the files when calling begin or size).

Please keep me posted.

Raffi Enficiaud — Thu, 18 Jan 2018 19:52:44 GMT

Any news?

Raffi Enficiaud — Sun, 11 Feb 2018 18:05:44 GMT

Kind reminder

Raffi Enficiaud — Wed, 27 Jun 2018 08:31:33 GMT

Closing, worst case related to #12953.

status changed; resolution set

Raffi Enficiaud — Wed, 01 Aug 2018 17:09:57 GMT

status new → closed
resolution → obsolete

Fixed via #12953