[issue10641] kill_python sometimes fails to kill processes on buildbots

2019-03-16 Thread Zachary Ware


Zachary Ware  added the comment:

As kill_python.exe has been removed from PCbuild/ and this hasn't been a 
problem in recent years, I'm going to go ahead and close the issue.

--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2019-03-15 Thread Mark Lawrence


Change by Mark Lawrence :


--
nosy:  -BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2015-02-19 Thread Mark Lawrence

Mark Lawrence added the comment:

I don't recall seeing this flagged anywhere else so can we close it as out of 
date?

--
components: +Windows -Build
nosy: +BreamoreBoy, steve.dower, tim.golden, zach.ware

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10641
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2015-02-19 Thread Steve Dower

Steve Dower added the comment:

Not sure if this still affects 2.7, but it doesn't affect 3.5 anymore. 

If one of the buildbot owners confirms that 2.7 is fine, I'll close.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10641
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2010-12-07 Thread Hirokazu Yamamoto

Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment:

To kill python_d.exe, you should use kill_python_d.exe instead of
kill_python.exe.

 On the XP and Win7 buildbots, kill_python sometimes fails to kill hung
 processes.

Could you post the buildbot log url?

--
nosy: +ocean-city

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10641
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2010-12-07 Thread Hirokazu Yamamoto

Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment:

I think #9973 is rather related.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10641
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2010-12-07 Thread David Bolen

David Bolen db3l@gmail.com added the comment:

 To kill python_d.exe, you should use kill_python_d.exe instead of
 kill_python.exe.

Crud, I thought I did.  Well, ok, so can't trust this test.

 Could you post the buildbot log url?

I think this is the last build in the sequence that was failing until I killed 
the processes:  
http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.x/builds/2297
  ... the processes had been around for maybe 45 hours at that point, but I 
can't find the last working run in the waterfall display (I get back to 2252 
and then it sort of goes blank).

Maybe the main problem is just the sequencing ... the fact that kill_python is 
only used at the start of a build (but after the svn step) and not during the 
clean step at the end of a test run?  In this case since the svn step was 
failing it probably never got as far as running kill_python[_d].

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10641
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2010-12-07 Thread David Bolen

David Bolen db3l@gmail.com added the comment:

 I think #9973 is rather related.

Certainly could be another artifact of a python_d process still executing. In 
particular though, the suggested patch in that issue agrees with what I was 
thinking might be needed, in terms of moving kill_python_d over to clean.bat.

Can't think of any downsides of applying that change offhand, so if that were 
to be made, we could just then watch and wait to see if another hung condition 
occurred.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10641
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10641] kill_python sometimes fails to kill processes on buildbots

2010-12-06 Thread David Bolen

New submission from David Bolen db3l@gmail.com:

On the XP and Win7 buildbots, kill_python sometimes fails to kill hung 
processes.  I caught one instance recently and gathered some information though 
not yet enough to identify the issue.  I can say that no processes are killed 
and no error messages displayed.  I think that implies either a process 
ownership-related snapshot failure (which can exit without error) or a failure 
to identify the processes.

I noticed issue10136 and considered it might be related, but in testing I found 
cases where the exact same usage of kill_python as this failing case worked 
fine, whereas if it was a path mismatch problem I would expect it to fail 
consistently. 

I have attached a log showing the hung processes, attempt to use kill_python, 
and final successful operation with the pskill utility.

In this case it was important to restore the buildbot quickly, but if I can 
catch it again I'll try to add some debugging code to kill_python first.

One thing that confused me along the way is that kill_python is only run at the 
beginning of a build and not as part of the clean process.  So there are cases 
where I have hung processes around, but they turn out to be killable when the 
next build starts.  I'm wondering if kill_python shouldn't perhaps be used on 
every clean operation too.

-- David

--
components: Build
files: kill_python.log
messages: 123510
nosy: db3l
priority: normal
severity: normal
status: open
title: kill_python sometimes fails to kill processes on buildbots
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2
Added file: http://bugs.python.org/file19964/kill_python.log

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10641
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com