[Report] 1 regressions on RC_1_34_0 (2007-04-01)

Boost Regression test failures Report time: 2007-04-01T02:22:36Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... 1 failures in 1 libraries parameter (1) |parameter| python_test: gcc-cygwin-3.4.4

Douglas Gregor <dgregor@osl.iu.edu> writes: | Boost Regression test failures | Report time: 2007-04-01T02:22:36Z | | This report lists all regression test failures on release platforms. | | Detailed report: | http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... | | 1 failures in 1 libraries | parameter (1) I already mentioned this "warning" error in another mail, but no response yet. Here is the patch. Index: boost/archive/detail/iserializer.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/archive/detail/iserializer.hpp,v retrieving revision 1.30.2.1 diff -u -r1.30.2.1 iserializer.hpp --- boost/archive/detail/iserializer.hpp 30 May 2006 15:56:35 -0000 1.30.2.1 +++ boost/archive/detail/iserializer.hpp 2 Apr 2007 09:49:47 -0000 @@ -121,7 +121,7 @@ return boost::serialization::implementation_level<T>::value >= boost::serialization::object_class_info; } - virtual bool tracking(const unsigned int flags) const { + virtual bool tracking(const unsigned int /*flags*/) const { // if(0 != (flags & no_tracking)) // return false; return boost::serialization::tracking_level<T>::value Index: boost/archive/detail/oserializer.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/archive/detail/oserializer.hpp,v retrieving revision 1.32.2.1 diff -u -r1.32.2.1 oserializer.hpp --- boost/archive/detail/oserializer.hpp 4 Jun 2006 14:51:24 -0000 1.32.2.1 +++ boost/archive/detail/oserializer.hpp 2 Apr 2007 09:49:47 -0000 @@ -114,7 +114,7 @@ return boost::serialization::implementation_level<T>::value >= boost::serialization::object_class_info; } - virtual bool tracking(const unsigned int flags) const { + virtual bool tracking(const unsigned int /*flags*/) const { // if(0 != (flags & no_tracking)) // return false; return boost::serialization::tracking_level<T>::value == boost::serialization::track_always -- Lgb

on Mon Apr 02 2007, larsbj-AT-gullik.net (Lars Gullik Bjønnes) wrote:
Douglas Gregor <dgregor@osl.iu.edu> writes:
| Boost Regression test failures | Report time: 2007-04-01T02:22:36Z | | This report lists all regression test failures on release platforms. | | Detailed report: | http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... | | 1 failures in 1 libraries | parameter (1)
I already mentioned this "warning" error in another mail,
There's no such thing as a warning error; that's just a warning. I have a bunch of warning fixes that I've been sitting on under the assumption that it's too late to make such trivial changes to code.
but no response yet.
If you want a response to a serialization library patch, put [serialization] in the subject line. You should also put it in the SF patch tracker and assign it to the library's author. -- Dave Abrahams Boost Consulting www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com

David Abrahams <dave@boost-consulting.com> writes: | on Mon Apr 02 2007, larsbj-AT-gullik.net (Lars Gullik Bjønnes) wrote: | | > Douglas Gregor <dgregor@osl.iu.edu> writes: | > | > | Boost Regression test failures | > | Report time: 2007-04-01T02:22:36Z | > | | > | This report lists all regression test failures on release platforms. | > | | > | Detailed report: | > | http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... | > | | > | 1 failures in 1 libraries | > | parameter (1) | > | > I already mentioned this "warning" error in another mail, | | There's no such thing as a warning error; that's just a warning. By not fixing warnings in the public api you are forcing users to allow warnings. | I have a bunch of warning fixes that I've been sitting on under the | assumption that it's too late to make such trivial changes to code. I see other warnings as well, but those comes from libs/xxx/src. Quite a different animal. | > but no response yet. | | If you want a response to a serialization library patch, put | [serialization] in the subject line. You should also put it in the SF | patch tracker and assign it to the library's author. Right... did that... no response. -- Lgb

on Mon Apr 02 2007, larsbj-AT-gullik.net (Lars Gullik Bjønnes) wrote:
David Abrahams <dave@boost-consulting.com> writes:
| on Mon Apr 02 2007, larsbj-AT-gullik.net (Lars Gullik Bjønnes) wrote: | | > Douglas Gregor <dgregor@osl.iu.edu> writes: | > | > | Boost Regression test failures | > | Report time: 2007-04-01T02:22:36Z | > | | > | This report lists all regression test failures on release platforms. | > | | > | Detailed report: | > | http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... | > | | > | 1 failures in 1 libraries | > | parameter (1) | > | > I already mentioned this "warning" error in another mail, | | There's no such thing as a warning error; that's just a warning.
By not fixing warnings in the public api you are forcing users to allow warnings.
I know; it's suboptimal.
| I have a bunch of warning fixes that I've been sitting on under the | assumption that it's too late to make such trivial changes to code.
I see other warnings as well, but those comes from libs/xxx/src. Quite a different animal.
I see.
| > but no response yet. | | If you want a response to a serialization library patch, put | [serialization] in the subject line. You should also put it in the SF | patch tracker and assign it to the library's author.
Right... did that... no response.
If it's in the tracker it will get dealt with eventually, but he's probably not too active now because everyone is holding their breath waiting for 1.34 to go out. -- Dave Abrahams Boost Consulting www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com
participants (3)
-
David Abrahams
-
Douglas Gregor
-
larsbj@gullik.net