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

Subject: Re: [boost] [1.40.0] Freeze for release candidate
From: Matthias Troyer (troyer_at_[hidden])
Date: 2009-08-25 15:45:11

On Aug 25, 2009, at 4:45 PM, Jeremiah Willcock wrote:

> On Tue, 25 Aug 2009, Vladimir Prus wrote:
>
>> Steve M. Robbins wrote:
>>
>>> On Tue, Aug 25, 2009 at 09:40:52AM +0400, Vladimir Prus wrote:
>>>> Belcourt, Kenneth wrote:
>>>
>>>>> That would be me.  But it sure looks like there's graph_parallel  
>>>>> and
>>>>> mpi results from Debian-Sid on Release.
>>>>>
>>>>> http://www.boost.org/development/tests/release/developer/summary.html
>>>>
>>>> Presumably because Steven's has manually tweaked the results  
>>>> again :-/
>>>
>>> Yes, I did.
>>
>> So, let me summarize the options we have at this point:
>>
>> 1. Decide that apparently, MPI tests were never run in past as part  
>> of regression
>> testing framework, and therefore can wait till 1.41.
>>
>> 2. Have Noel try running with trunk version of XSL scripts, either  
>> using "svn switch",
>> or by merging to release branch. Then, fix MPI failures.
>>
>> Can the release management team decide?
>>
>> Incidentally, I wonder if (2) is necessary for fixing MPI failures.  
>> Jeremiah,
>> do you get clean MPI test run locally? If not, maybe you can start  
>> to fix
>> failures pro-actively?
>
> Using the Intel compiler version 10 on Linux, I get a static  
> assertion failure in save_enum() line 65 in boost/mpi/detail/ 
> mpi_datatype_oarchive.hpp when trying to compile ring_test.   
> However, when I use a different method of checking the equality of  
> the two sides of the comparison, it works just fine.  Is  
> MPL_STATIC_ASSERT broken on that platform?  Can anyone else with  
> more experience find out what is going on there?  Thank you.

I have no knowledge of MPL_STATIC_ASSERT, but would suggest that one  
can just add a workaround for that compiler in ring_test'

Matthias