Boost C++ Libraries: Ticket #1723: No subprocess can be started in init_unit_test_suite

status changed; resolution set

Gennadiy Rozental — Mon, 07 Jul 2008 03:21:55 GMT

status new → closed
resolution → fixed

fixed in svn already

anonymous — Wed, 20 Aug 2008 07:31:16 GMT

This bug does not seem to be fixed in Boost 1.36.0. I still obtain errors when child processes exit with return code 0.

Test setup error: child has exited; pid: 503; uid: 26975; exit value: 0

anonymous — Wed, 20 Aug 2008 14:36:49 GMT

You can disable catching this error with the environment variable BOOST_TEST_CATCH_SYSTEM_ERROR=no

attachment set

tim@… — Thu, 11 Sep 2008 11:25:34 GMT

attachment → 0001-fix-for-boost.test.patch

fix for 1.36

anonymous — Fri, 26 Sep 2008 10:55:55 GMT

I'm finding that the patch prevents the error message but doesn't cause the code after the system() call (within the BOOST_AUTO_TEST_CASE) to be executed.

For example:

BOOST_AUTO_TEST_CASE(MyTestCase) {
	cerr << "Before command" << endl;
	system("echo Command");
	cerr << "After command" << endl;
	BOOST_CHECK_EQUAL(1, 1);
}

...gives output which includes the following...

Entering test case "MyTestCase"
Before command
Command
Test case MyTestCase doesn't include any assertions
***************************************************
Leaving test case "MyTestCase"

This is the case after I have applied the patch and set the environment variable BOOST_TEST_CATCH_SYSTEM_ERROR to "no".

Thanks very much for your help.

anonymous — Mon, 06 Oct 2008 05:08:22 GMT

Replying to anonymous:

You can disable catching this error with the environment variable BOOST_TEST_CATCH_SYSTEM_ERROR=no

Not that this should be

BOOST_TEST_CATCH_SYSTEM_ERRORS=no rather than BOOST_TEST_CATCH_SYSTEM_ERROR=no