Re: [Boost-testing] Re: --monitored not working

From: Victor A. Wagner Jr. (vawjr_at_[hidden])
Date: 2005-05-31 15:55:38

At 13:10 2005-05-31, you wrote:

>"Aleksey Gurtovoy" <agurtovoy_at_[hidden]> wrote in message
>news:m1wtpf4ldc.fsf_at_tulip.office.meta...
> > Beman Dawes writes:
> >> On a Win XP SP2 machine with a hyper-threaded Intel P4, I run the
> >> regression
> >> tests with this command:
> >>
> >> python
> >> regression.py --runner=Beman --incremental --monitored 
> --toolsets=cw-9_4,gcc,intel-win32-8_1
> >>
> >> It looks like the monitor starts running (in a separate command
> >> window), but in the morning (after an overnight run) the monitor is
> >> gone and I have to kill each dialog box by hand.
> >
> > Has your run completed by then, though? IOW, were the dialogs holding
> > the regression process, or they were just "leftovers"?
>
>They were holding the regression process. The process had not completed, and
>there was no system activity showing on the task manager performance
>display. As I cleared each dialog, there was activity until the next dialog,
>then no activity until it was cleared.

my system (details at the RudbekAssociates link in the results page) 
behaves differently.  I wake up in the morning with several "dialog boxes" 
waiting for me to click on, but the tests have completed.

>--Beman
>
>
>
>_______________________________________________
>Boost-Testing mailing list
>Boost-Testing_at_[hidden]
>http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Victor A. Wagner Jr.      http://rudbek.com
The five most dangerous words in the English language:
               "There oughta be a law"