Re: [Boost-users] setup_error: test unit with name 'free_test_function' registered multiple times

Subject: Re: [Boost-users] setup_error: test unit with name 'free_test_function' registered multiple times
From: Raffi Enficiaud (raffi.enficiaud_at_[hidden])
Date: 2018-06-26 19:37:08

Le 04/05/2018 à 14:49, dinesh kumar via Boost-users a écrit :
> Hi Team,
> [snip]
> 
> Hi Team,
> 
> Greetings for the day.
> 
> I apologies if this is a duplicate case which is already reported, but I 
> am unable to find a suitable answer for this.
> 
> I have installed boost(1.67.0.1 <http://1.67.0.1>) via brew, and created 
> a simple unit test case as below.
> 
> #define BOOST_TEST_DYN_LINK
> #define BOOST_TEST_MODULE super
> #include <boost/test/unit_test.hpp <http://test.hpp>>
> 
> using namespace boost::unit_test;
> 
> std::string uri;
> std::string versionNum;
> 
> BOOST_AUTO_TEST_CASE( free_test_function ) {
>  Â Â Â  BOOST_CHECK(true /* test assertion */);
> }
> 
> _Compiled this code as below._
> 
> g++ obj/main.o -LÂ  /Library/PostgreSQL/9.6/lib -L /usr/local/lib -L 
> /usr/local/opt/openssl/lib/Â  -o test_integration -lpq -lcpprest 
> -lboost_regex-mt -lboost_system-mt -lboost_thread-mt -lssl -lcrypto 
> -lboost_chrono-mt -lboost_log-mt -lboost_locale-mt -lboost_date_time-mt 
> -lboost_program_options-mt -lboost_stacktrace_noop-mt 
> -lboost_filesystem-mt -lboost_unit_test_framework-mt
> test integration installation is completed.
> 
> 
> _Got the error, while I execute the binary._
> 
> ./test_integration
> libc++abi.dylib <http://abi.dylib>: terminating with uncaught exception 
> of typeboost::unit_test::framework::setup_error: test unit with name 
> 'free_test_function' registered multiple times
> [1]    59619 abort      ./test_integration
> _
> _

In 1.67, a sanity check has been introduced, and this is fired exactly 
because of the reason mentioned.

Now, it sounds like there are other files that are getting included in 
the build. For instance, the free_test_function is mentioned several 
times in the examples.

Would you please rename the test to something else and check again? 
Otherwise, I have no clue what is going on.

Raffi