From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-03-07 05:35:33
On Tuesday 07 March 2006 12:09, Reece Dunn wrote:
> NOTE: In the V1 regression run, the iostream compression library tests are
> skipped (leaving the entry white) if the libraries don't exist. This could
> be done using something like:
> rule comp-test ( compression : sources )
> if ! $(NO_$(compression))
> return [ run $(compression)_test : $(sources) ] ;
> return ;
> (this hasn't been verified, though). That would make it consistent with V1
> and cut the errors in half!
I'll see about this.
> >For safety, I'd prefer to try some approached with Python tests and then
> >until Reece does another run with msvc, and after that we can start asking
> >regular regression runners to switch. Because of the current state of
> > MSVC, I
> >expect no problems, and the whole processs should be finished in a week or
> As I mentioned above, I have started another msvc run now. Let me know when
> the other changes are in so I can restart it.
There are fixes to two Python tests (as mentioned in the "Last Python issues")
It would be great if you verify that those tests work before investing CPU
cycles on full test run.
> Having had several run throughs with running the regression tests, I am now
> at the point where I can run the tests once every day, provided that the
> BBv2 tests aren't broken.
> BTW: if there is a BBv2 problem (e.g. like the previous ptr_container
> problem), this doesn't get logged by the regression script. It would be
> useful if this could be captured and displayed on the regression results
> table to save me or others from posting the issue directly.
I'm not sure how to arrange this, yes, and even where to report this
enhancement request :-( Maybe, the SF tracker can be used, or the Wiki,
I need to check on boost-testing.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk