[Webkit-unassigned] [Bug 39203] [DRT/Chromium] Increase the time out value

[bugzilla-daemon at webkit.org]

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





--- Comment #3 from Kent Tamura <tkent at chromium.org>  2010-05-17 02:16:52 PST ---
(In reply to comment #2)
> Ojan would be a good reviewer since he did a lot of work on getting the timeout as low as possible in TestShell.
> 
> I'm a little confused.  I thought when we hit the timeout, we first call notifyDone, and if that fails, we exit(0) the process (which looks like a crash).  Is the call to notifyDone failing?

I think DRT/Chromium works as the same as other platforms DRTs.

The problem is that, if a DRT process exits before new-run-webkit-tests detects timeout, new-run-webkit-tests assumes the DRT process crashed.
(webkitpy/layout_tests/port/server_process.py _read())

The current DRT/Chromium timeout value is 10 sec and new-run-webkit-tests timeout value is 6 sec. I'm not sure why new-run-webkit-tests can't detect timeout correctly.  Anyway, making DRT timeout value longer solves the problem.

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