|
|
Boost Testing : |
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-11-20 19:57:06
Thomas Witt wrote:
> AlisdairM wrote:
>> John Maddock wrote:
>>
>>> OK, I hadn't realised it was a release build, I can reproduce now,
>>> looks like a known linker bug:
>>> http://qc.borland.com/wc/qcmain.aspx?d=32020 that occurs when the
>>> project exceeds a certain size. I guess I'll just have to mark them
>>> up as expected :-(
>> I'm not sure that is the right answer - at least not for Boost 1.34.
>>
>> I am concerned that JustSoftwareSolutions are not so much reporting
>> regressions, as running tests in new configurations - release builds.
>>
>> This is an incredibly valuable contribution, but nailing these problems
>> is new work, not fixing regressions. Given that we really want to ship
>> 1.34 sooner rather than later, I would suggest this test runner focus
>> back on the mainline, and we pay attention to release-configuration
>> issues for 1.35.
>
> FWIW I do agree with Alisdair.
What I was doing in the past was tagging the toolset with a clear marker
that I was doing release builds. This prevented those runs from
getting considered as part of the release toolsets. Either adding
"~release" or "_release" to the toolset version works.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo