Re: [Boost-testing] broken reporting of failure expectations

From: Beman Dawes (bdawes_at_[hidden])
Date: 2005-07-09 20:55:52

"Douglas Gregor" <doug.gregor_at_[hidden]> wrote in message 
news:c5e98d3c788eb71bd4d89782f270fd2d_at_cs.indiana.edu...
>
> On Jul 9, 2005, at 5:22 PM, Beman Dawes wrote:
>
>>
>> "David Abrahams" <dave_at_[hidden]> wrote in message
>> news:uhdfb2old.fsf_at_boost-consulting.com...
>>
>>> Also, an aside, it appears that OSL's gcc-3_3-darwin and BGDX's
>>> gcc-3_3-apple are identical.  weren't we trying to avoid duplicate
>>> testing?
>
> For Dave: I'd like to avoid duplicate testing when it results in slower
> throughput, e.g., Martin Wille's tests were taking a *really* long time
> to cycle.
>
>> I'd like to run BGDX several times a day, so that developers don't
>> have to
>> wait so long for results to cycle. The only reason I haven't been
>> doing that
>> is that I couldn't get cron to start. I've been meaning to try again,
>> but
>> got distracted.
>
> You should rename gcc-3_3-apple to gcc-3_3-darwin, because some
> Jamfiles (e.g., Python) look for the "darwin" part of the name.

OK, done, although the Apple tests have been running without problems and 
are being reported correctly.

It is the Windows test that is failing to find the .jam file.

--Beman