Re: [boost] [1.40.0] Freeze for release candidate

Subject: Re: [boost] [1.40.0] Freeze for release candidate
From: Eric Niebler (eric_at_[hidden])
Date: 2009-08-24 13:03:00

Vladimir Prus wrote:
> Jeremiah Willcock wrote:
>> On Mon, 24 Aug 2009, Eric Niebler wrote:
>>> Jeremiah Willcock wrote:
>>>> On Mon, 24 Aug 2009, Beman Dawes wrote:
>>>>
>>>>> As far as I can tell, all the branches/release merges we were waiting
>>>>> for have now been completed. The plan is to go ahead with the release
>>>>> candidate as soon as all the release branch tests have cycled for
>>>>> revision 55757.
>>>>>
>>>>> Please commit no more changes to branches/release without explicit
>>>>> permission from me.
>>>> One issue that I am concerned about is that there are no regression test
>>>> results for the release branch with MPI (and thus Boost.MPI and
>>>> Boost.Graph.Parallel) turned on.  Thus, neither of these components have
>>>> been tested in a couple of weeks, and they were broken last time the
>>>> regression tests ran for them.  I would feel more comfortable if the
>>>> regression tests passed for those before the release as well.  What are
>>>> other peoples' opinions on that?
>>> Someone would need to step forward to run them. If someone did that Soon (in
>>> the next few days), I'm pretty sure we would be happy to hold the release for
>>> a test cycle. Do we have any volunteers?
>> Steve Robbins was running them (and probably still is), but the results
>> were not being reported to the regression testing site.  There was a
>> discussion on boost-testing about the issue: "[Boost-testing] test results
>> with mpi vanish", but I do not believe that the bug in the Web site was
>> ever resolved to allow the tests to appear.
> 
> I believe it was resolved, and there was at least one fairly green run from
> Steven. The current results are unwell:
> 
> http://www.boost.org/development/tests/trunk/developer/output/Debian-Sid-boost-bin-v2-libs-mpi-test-all_gather_test-1-test-gcc-4-3-4-debug-threading-multi.html
> 
> But it seems due to genuine code-level problem.

On the release branch, boost/archive/detail/iserializer.hpp does not 
include boost/archive/detail/check.hpp, which seems to indicate to me 
that this tester is either testing old code or else is not testing the 
release branch at all. Can someone comment? Steve?

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com