From: Reece Dunn (msclrhd_at_[hidden])
Date: 2006-02-15 12:35:44
Vladimir Prus wrote:
>On Wednesday 15 February 2006 00:15, Reece Dunn wrote:
> > Hi All,
> > I haven't posted test results tonight because they aren't completed yet!
> > The V2/serialzation tests are unable to locate the serialization DLL :(.
> > This meant that Windows displayed an error message dialog informing me
> > that fact and not continuing with the build.
>This suprised me, as in Alexey's tests the problems appeared only on wide
>archive tests. Are you sure you're using the very latest version?
I was getting the above problem for the wide archive DLLs - sorry, I should
have been more specific.
>Does libs/serialization/build/Jamfile.v2 contain settings of
Not sure: I'll check when I next get to the machine running the tests.
> > This leads me to wonder... is it possible to start the test executable
> > one thread and monitor it's progress in the main thread. If the
> > exits, great; if it brings up a dialog (and the test is not marked as
> > 'gui'), grab the text on that dialog (outputting it along with an error
> > message) and close it (via an IDCANCEL command message) and kill the
> > otherwise, if a timeout occurs, log a timeout and kill the test process.
>I think there's such monitor that can be used by regression.py script. I
>say at the moment how it works or even how to get it, unfortunately.
> > NOTE: I am not sure how to apply this to other OSes like Linux and Mac.
>On Linux, there are no automatic popup messages, generally.
The current test run are being run after deleting the bin and bin.v2
directories. The previous ones were run on top of a previous build. I'll see
what happens tonight.
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