Boost.Thread test results in Boost.Tokenizer
Hi, I'm looking at Boost.Tokenizer trunk test results. For some reason, Sandia-intel-10.1 column contains test "examples" which result refers to some Boost.Thread test: <http://www.boost.org/development/tests/trunk/developer/output/Sandia-intel-10-1-boost-bin-v2-libs-tokenizer-test-examples-test-intel-darwin-10-1-debug.html> Does anyone know how that happened and how to fix it?
On Aug 21, 2010, at 2:56 AM, Andrey Semashev wrote:
I'm looking at Boost.Tokenizer trunk test results. For some reason, Sandia-intel-10.1 column contains test "examples" which result refers to some Boost.Thread test:
<http://www.boost.org/development/tests/trunk/developer/output/Sandia-intel-1...
Does anyone know how that happened and how to fix it?
No and no. I first noticed this problem about 6 weeks ago when looking at the MPI test results and finding MPL test results instead. Unfortunately I can't point you to the MPI problem because most all MPI is broken due to errors in serialization. I do know that the machine generating the trunk and release reports has not been updated or modified so XSLT and other tools have not changed. It seems this reporting problem only exists in trunk reporting, I haven't seen this in the release reporting. -- Noel
On Aug 21, 2010, at 12:33 PM, "Belcourt, Kenneth" <kbelco@sandia.gov> wrote:
On Aug 21, 2010, at 2:56 AM, Andrey Semashev wrote:
I'm looking at Boost.Tokenizer trunk test results. For some reason, Sandia-intel-10.1 column contains test "examples" which result refers to some Boost.Thread test:
Does anyone know how that happened and how to fix it?
No and no. I first noticed this problem about 6 weeks ago when looking at the MPI test results and finding MPL test results instead. Unfortunately I can't point you to the MPI problem because most all MPI is broken due to errors in
I thought we fixed those errors for 1.44. Are there new problems? Matthias
I do know that the machine generating the trunk and release reports has not been updated or modified so XSLT and other tools have not changed. It seems this reporting problem only exists in trunk reporting, I haven't seen this in the release reporting.
-- Noel
___________
On Aug 21, 2010, at 1:37 PM, Matthias Troyer wrote:
On Aug 21, 2010, at 12:33 PM, "Belcourt, Kenneth" <kbelco@sandia.gov> wrote:
On Aug 21, 2010, at 2:56 AM, Andrey Semashev wrote:
I'm looking at Boost.Tokenizer trunk test results. For some reason, Sandia-intel-10.1 column contains test "examples" which result refers to some Boost.Thread test:
<http://www.boost.org/development/tests/trunk/developer/output/Sandia-intel-1...
Does anyone know how that happened and how to fix it?
No and no. I first noticed this problem about 6 weeks ago when looking at the MPI test results and finding MPL test results instead. Unfortunately I can't point you to the MPI problem because most all MPI is broken due to errors in
I thought we fixed those errors for 1.44. Are there new problems?
Yes, compile problems with serialization/access.hpp. instantiated from here ../boost/serialization/access.hpp:118: error: ???class std::list<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >??? has no member named ???serialize??? http://tinyurl.com/25bhe8d -- Noel
On 21 Aug 2010, at 21:42, Belcourt, Kenneth wrote:
On Aug 21, 2010, at 1:37 PM, Matthias Troyer wrote:
On Aug 21, 2010, at 12:33 PM, "Belcourt, Kenneth" <kbelco@sandia.gov> wrote:
No and no. I first noticed this problem about 6 weeks ago when looking at the MPI test results and finding MPL test results instead. Unfortunately I can't point you to the MPI problem because most all MPI is broken due to errors in
I thought we fixed those errors for 1.44. Are there new problems?
Yes, compile problems with serialization/access.hpp.
instantiated from here ../boost/serialization/access.hpp:118:
error: ???class std::list<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >??? has no member named ???serialize???
This is actually a regression in Boost.Serialization and lots of serialization tests fail with the same error message. Matthias
participants (3)
-
Andrey Semashev -
Belcourt, Kenneth -
Matthias Troyer