Hi Gennadiy, On Oct 3, 2011, at 2:09 PM, Gennadiy Rozental wrote:
Dave Abrahams <dave <at> boostpro.com> writes:
This is so obvious, and things like this have happened so many times, that I'm amazed they're still happening.
Not sure what you refer to. I did not make any major changes for many many years.
I wish that were the case Gennadiy. In actuality though, I sent you this email (partially reproduced below) following your large commit last May that caused, and continues to cause, significant problems for the MacOSX Intel toolset. I did copy you on this email. On May 18, 2010, at 3:12 PM, Belcourt, Kenneth wrote:
Hi,
The Sandia Darwin Intel testers have been stable for some time but a recent change seems to have broken the tester. This test in Boost.Test, seems to be the source of the problem (test_tools_test).
brisc: kbelco$ pwd /Volumes/Scratch/kbelco/boost/results/boost/bin.v2/libs/test/test/ test_tools_test.test/intel-darwin-11.0/debug
brisc: kbelco$ more test_tools_test.output terminate called after throwing an instance of 'boost::system_error' Running 22 test cases... terminate called recursively
-- Noel