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

From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2007-02-04 03:22:14

"David Abrahams" <dave_at_[hidden]> wrote in message 
news:87sldnxqek.fsf_at_valverde.peloton...
> Rene Rivera <grafikrobot_at_[hidden]> writes:
>
>> David Abrahams wrote:
>>> Rene Rivera <grafikrobot_at_[hidden]> writes:
>>>
>>>> David Abrahams wrote:
>>>>> Rene Rivera <grafikrobot_at_[hidden]> writes:
>>>>>
>>>>>> David Abrahams wrote:
>>>>>>> I recently started a "monitored" test run, went away for a while, 
>>>>>>> and
>>>>>>> came back to find only the build monitor still running.  I remember
>>>>>>> people had trouble with this a while back.  Did we ever find a cure?
>>>>>> Yes. Use the "-lx" option of bjam instead.
>>>>> it's not in the --help documentation.  What does it do?
>>>> http://engineering.meta-comm.com/resources/cs-win32_metacomm/doc/html/jam/usage.html#jam.usage.options
>>>
>>> Hmm, it's not seeming to kill off the assertion dialog that one of my
>>> tests produces.  Am I missing something?
>>
>> Hm, there is code to try and close off those dialogs. I didn't write
>> that part of the code so I'd only be guessing why it doesn't work in
>> your case.
>
> Who did write it?  I still have these dialogs hanging around from
> crashed tests.

I am working on an extensive update for the execution monitor. It may or may 
not address an issue of process hanging. Is there any way to produce 
comparatively simple example that exhibit this behavior?

Gennadiy