[Webkit-unassigned] [Bug 53220] back-during-onload-hung-page.php causes Chromium WebKit bot to fail

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=53220


Tony Chang <tony at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tony at chromium.org




--- Comment #6 from Tony Chang <tony at chromium.org>  2011-01-27 11:54:31 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > I take it we don't have code in run-webkit-tests/new-run-webkit-tests to kill run-away http servers (or in this case php processes?)  Should we?
> 
> I don't know much about those scripts, but they appear to try to kill the process but fail in this case.  Here's one of the error messages from the bot, which looks like it tried and failed to kill the PHP process (according to Nicolas, who found out which process it was after the fact):
> 
> command timed out: 600 seconds without output, killing pid 19192
> SIGKILL failed to kill process
> using fake rc=-1
> program finished with exit code -1

Maybe I misunderstand, but it looks like the buildbot process is trying to kill the NRWT process.  Maybe it's failing to kill the NRWT because it's holding on to the lighttpd process which holds on to the php process?  I bet it wouldn't be too hard to add a "kill all php.exe processes" when stopping the httpd, but it might cause collateral damage.

I bet apache handles this better.  Another reason to try and switch to apache (although I'm not volunteering).

Nice detective work!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.