From: David Abrahams (dave_at_[hidden])
Date: 2002-07-25 06:24:08
From: "Beman Dawes" <bdawes_at_[hidden]>
> One of the challenges remaining for bjam-based regression testing is
> able to detect that a test has failed because a library it depends on
> failed to build, and to report the compiler or other error messages which
> indicate why the library build failed.
> The current system already provides the error messages. What is missing
> a notification like:
> "x failed because it depends on y, which failed".
> x and y are the target directory paths.
The system already says "skipping <x> due to missing <y>"
The paths are not /exactly/ represented, but you can figure them out from
<x> and <y>.
> x can be omitted if the message is part of the residue left in directory
> it is only needed if the message is in the bjam log output.
> The exact format of the message is unimportant as long as it is
> and reasonably easy to extract x and y from it. It does need to work
> if a test is dependent on several libraries, and more than one fails to
> Is it reasonable to ask for this with V1 or is it something that will
> to be deferred until V2?
If you want something more-sophisticated than what it's doing now, it'll
have to wait. However, this is one of those things that really needs core
Jam enhancements in order to do it right. That's why the requirements
document we discussed would be a big help - we need to gather all the
required behaviors in one place so we can see what needs to be
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