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

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

Bronek Kozicki <brok_at_[hidden]> writes:

> David Abrahams wrote:
>>> the code to close alerts is "only" few months old, so if you are using 
>>> older build of boost
>> 
>> You mean bjam?  
>
> yes.
>
>> It was built within the last few weeks; but I'll build
>> a new one.
>
> you have this new functionality.
>
>> I'm running my tests from a .bat script that gets run as a "Scheduled
>> Task."
>
> that's the problem. Scheculed Task is running in its own desktop, but 
> assertions are displayed on interactive desktop thus bjam canne access 
> them. Which whould you prefer:
> - running bjam as SYSTEM (you'd need to use command "at" to schedule it, 
> because there is no way to set SYSTEM user from GUI) and let bjam 
> iterate through all desktops each few secs
> - install new service and let bjam script "register" itself in this 
> service asking to kill all dialogs displayed by child processes

Keeping in mind that I really don't know much about the details of
what you're describing, the first way sounds easy but dangerous, and
the 2nd one sounds somehow safer and less-intrusive.  Is that right?
If so, I'd prefer the 2nd.

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