Re: [Boost-testing] Build monitor killed my test?

From: David Abrahams (dave_at_[hidden])
Date: 2007-02-06 12:23:46

Rene Rivera <grafikrobot_at_[hidden]> writes:

> David Abrahams wrote:
>> Well, I'm afraid we really need that "way around" if we're going to
>> have effective automated testing on Windows.  Otherwise a crashed test
>> stalls the whole process; a new test run won't start until all those
>> dialogs are closed.
>
> I don't believe that's true, at least on Win2K. The debug/assert popups 
> are put up by a a debugger process, not the process that crashes, and 
> hence not a process that is reachable through the usual parent/child 
> process hierarchy. That means that when the dialogs come up, bjam is 
> still running, it's just the crashed program that isn't. 

Yes, that's what I see on XP too.  However, that's not the problem.

The problem is that the *Scheduled Task* doesn't run again until the
dialogs are closed :(

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com