On Sunday 25 January 2015 23:04:44 Gennadiy Rozental wrote:
Andrey Semashev
writes: Also, there were lots of warnings on MSVC like here:
http://www.boost.org/development/tests/develop/developer/output/teeks99-> 08f-win2012R2-64on64-boost-bin-v2-libs-atomic-test-atomicity-test-msvc-14-0- debug-threading-multi.html
The same thing: "Error extracting file: No matching files were found."
Are you sure are were looking at correct reports? I found these being updated pretty slowly.
Same thing, the reports have been updated. Here are the warnings from another tester: call "c: \users\boost\appdata\local\temp\boost_regression\b2_msvc_12.0_vcvarsall_x86.cmd"
nul cl /Zm800 -nologo @"D: \local\teeks99-08\e\results\boost\bin.v2\libs\atomic\test\atomicity.test\msvc-12.0\debug\threading- multi\atomicity.obj.rsp"
atomicity.cpp D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(62) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_start' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(37) : see previous definition of 'log_start' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(72) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_finish' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(38) : see previous definition of 'log_finish' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(80) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_build_info' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(39) : see previous definition of 'log_build_info' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(93) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::test_unit_start' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(41) : see previous definition of 'test_unit_start' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(105) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::test_unit_finish' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(42) : see previous definition of 'test_unit_finish' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(125) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::test_unit_skipped' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(43) : see previous definition of 'test_unit_skipped' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(135) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_exception_start' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(45) : see previous definition of 'log_exception_start' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(163) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_exception_finish' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(46) : see previous definition of 'log_exception_finish' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(171) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_entry_start' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(48) : see previous definition of 'log_entry_start' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(208) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_entry_value' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(49) : see previous definition of 'log_entry_value' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(216) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_entry_value' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(50) : see previous definition of 'log_entry_value' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(224) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_entry_finish' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(51) : see previous definition of 'log_entry_finish' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(236) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::print_prefix' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(58) : see previous definition of 'print_prefix' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(253) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::entry_context_start' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(53) : see previous definition of 'entry_context_start' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(261) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::entry_context_finish' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(55) : see previous definition of 'entry_context_finish' D: \local\teeks99-08\e\boost_root\boost/test/impl/compiler_log_formatter.ipp(269) : warning C4273: 'boost::unit_test::output::compiler_log_formatter::log_entry_context' : inconsistent dll linkage D: \local\teeks99-08\e\boost_root\boost/test/output/compiler_log_formatter.hpp(54) : see previous definition of 'log_entry_context' ...and it goes on. http://www.boost.org/development/tests/develop/developer/output/teeks99-08e-...
Anyway, I decided to remove Boost.Test from Boost.Atomic tests.
You are free to do so, but just to make record strait: the issues in that case were caused by regression in Boost.Timer and minor misconfiguration in Boost.Thread.
At least Boost.Atomic tests were also affected, and there was a pull request fixing that. I can see a list of multiple affected libraries in this discussion.
BTW I thought one of the main reason to move toward modular boost was the ability to build/test against master version of the dependencies. Why is this still not the case?
Well, that's not me to ask, but personally I can see benefits of both approaches.