[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





--- Comment #3 from Charles Reis <creis at chromium.org>  2011-01-27 09:57:59 PST ---
(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

remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last):
Failure: buildbot.slave.commands.TimeoutError: SIGKILL failed to kill process
]


(From: http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Win%20(deps)/builds/334/steps/webkit_tests/logs/stdio)

Maybe we just need a more effective approach for killing such processes?  We only see the problem on one of the bots, so it might be specific to something in the config.

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