Hirokazu Yamamoto writes:
> Yes, but test can freeze. In that case, I'm worried that
> (snip)
> rt.bat # freeze here (will be halt by buildbot)
> vcbuild & kill_python_d # Will this be called?
> in test.bat.
Yeah, you're right. It may be impossible to completely eliminate the
ri
On 2010/12/08 0:11, David Bolen wrote:
In thinking about it some more, I suppose there's still a small window
for a loss of communication during a test which results in clean not
being run (which could then block the next svn checkout without an
opportunity to kill the processes), so maybe the ri
Tres Seaver writes:
> Maybe belt-and-suspenders it in both places.
The clean batch file is also called from the build step, so relocating it
there should maintain the existing behavior as well.
Hirokazu (ocean-city) pointed out in my new issue an earlier issue he
created (#9973) that included a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/2010 07:24 PM, David Bolen wrote:
> I previously wrote:
>
>> I suspect the problem may be on the "identify which process to kill"
>> rather than the "kill it" part, but it's definitely going to take time
>> to figure that out for sure. While
I previously wrote:
> I suspect the problem may be on the "identify which process to kill"
> rather than the "kill it" part, but it's definitely going to take time
> to figure that out for sure. While the approach kill_python takes is
> much more appropriate, since we don't currently have multipl
