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

Subject: Re: [boost] [1.40.0] Freeze for release candidate
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2009-08-25 01:10:54

Marshall Clow wrote:

> 
> On Aug 24, 2009, at 10:05 AM, Eric Niebler wrote:
> 
>> Marshall Clow wrote:
>>> On Aug 24, 2009, at 9:28 AM, Eric Niebler wrote:
>>>> Jeremiah Willcock wrote:
>>>>> 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?
>>> Eric -
>>> I can run a darwin test cycle tonight, if that helps.
>>
>> If you can get results for Boost.MPI and Boost.Graph.Parallel, then
>> yes, it helps. Thanks, Marshall.
> 
> Sigh, I got bit by <https://svn.boost.org/trac/boost/ticket/2185> -
> hang while linking python tests.

Got a backtrace? You might need to build bjam with debug information,
using "build.sh --debug" for a useful backtrace.

- Volodya