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:40:52

Belcourt, Kenneth wrote:

> 
> On Aug 24, 2009, at 11:22 PM, Vladimir Prus wrote:
> 
>> Steve M. Robbins wrote:
>>
>>>>> 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,
>>>
>>> It was resolved for trunk only, not for release.  I'm building
>>> "Debian-Sid" for both trunk and release -- with MPI configured -- for
>>> weeks now, but the results only show on trunk.
>>
>> Oh, that's fun. For all I can tell, everything should be using trunk
>> version of XSL scripts. Who is running the reporting script for
>> release,
>> and how exactly?
> 
> 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 :-/
Is the boost_wide_report.py script run from release checkout? This
might explain the situation, as it's apparently the only script that
does not fetch XSL things from trunk.

- Volodya