[1.45][thread] TSS showstopper?

The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests: testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run ====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error **** error return code: -1 ******** errors detected; see standard output for details ******** EXIT STATUS: 1 ====== END OUTPUT ====== I assume it's quite likely that if this effects the regex lib, then it will equally impact on user code that uses thread_specific_pointer? Regards, John.

On 11/11/2010 1:34 PM, John Maddock wrote:
The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests:
testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run
====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error
**** error return code: -1 ******** errors detected; see standard output for details ********
EXIT STATUS: 1 ====== END OUTPUT ======
I assume it's quite likely that if this effects the regex lib, then it will equally impact on user code that uses thread_specific_pointer?
Yes, the relevant showstopper bug was reopened this morning: https://svn.boost.org/trac/boost/ticket/4736 Anthony? -- Eric Niebler BoostPro Computing http://www.boostpro.com

John Maddock <boost.regex@virgin.net> writes:
The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests:
testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run ====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error
**** error return code: -1 ******** errors detected; see standard output for details ********
EXIT STATUS: 1 ====== END OUTPUT ======
I assume it's quite likely that if this effects the regex lib, then it will equally impact on user code that uses thread_specific_pointer?
Gah! That means there's something wrong with the fix I applied recently :-( I'll look into it. Anthony -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

John Maddock <boost.regex@virgin.net> writes:
The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests:
testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run ====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error
I've fixed that on trunk, revision 66518. Anthony -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

On 11/12/2010 5:04 AM, Anthony Williams wrote:
John Maddock <boost.regex@virgin.net> writes:
The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests:
testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run ====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error
I've fixed that on trunk, revision 66518.
FWIW, this is now the last showstopper for 1.45. Is there any way of getting expedited results for regex and thread on msvc-10, so we can get this moved to release ASAP? -- Eric Niebler BoostPro Computing http://www.boostpro.com

Eric Niebler <eric@boostpro.com> writes:
On 11/12/2010 5:04 AM, Anthony Williams wrote:
John Maddock <boost.regex@virgin.net> writes:
The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests:
testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run ====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error
I've fixed that on trunk, revision 66518.
FWIW, this is now the last showstopper for 1.45. Is there any way of getting expedited results for regex and thread on msvc-10, so we can get this moved to release ASAP?
FYI: I'm going to be mostly offline until Monday, so probably won't be able to merge to release until then. Anthony -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

Anthony Williams <anthony.ajw@gmail.com> writes:
John Maddock <boost.regex@virgin.net> writes:
The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests:
testing.capture-output ..\..\..\bin.v2\libs\regex\test\regex_regress_threaded.test\msvc-10.0\debug\asynch-exceptions-on\threading-multi\regex_regress_threaded.run ====== BEGIN OUTPUT ====== TSS Initialisation failed with message: boost::thread_resource_error
I've fixed that on trunk, revision 66518.
Merged to release, revision 66588. Anthony -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++0x thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

On 11/15/2010 5:14 AM, Anthony Williams wrote:
Anthony Williams <anthony.ajw@gmail.com> writes:
John Maddock <boost.regex@virgin.net> writes:
The recent changes to Boost.Thread in both Trunk and Release branches have broken one of the regex tests:
I've fixed that on trunk, revision 66518.
Merged to release, revision 66588.
Thanks, Anthony. With the above change, we've driven the showstopper count to zero for 1.45. Congrats everybody. Beman, what do you say we wait for a test cycle and then ship this thing? -- Eric Niebler BoostPro Computing http://www.boostpro.com
participants (3)
-
Anthony Williams
-
Eric Niebler
-
John Maddock