[Webkit-unassigned] [Bug 96342] "FAIL: Timed out waiting for notifyDone to be called" should be TIMEOUT failures, not TEXT

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 10 21:30:06 PDT 2012


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





--- Comment #3 from Dirk Pranke <dpranke at chromium.org>  2012-09-10 21:30:28 PST ---
(In reply to comment #1)
> Logically this makes sense.
> 
> My only concern is that a timeout currently usually means the process hung, whereas these bugs usually mean the test didn't complete for some other reason.  Thus a current timeout is much more serious bug than these failures are.

Historically, in chromium (when we ran with TestShell instead of DRT) the timeout was enforced by TestShell itself, and things basically ran until the watchdog fired, much like with this error.

The only reason we assume the process is hung now is because we can't distinguish between a hung process and the case where we know DRT timed itself out. We could consider this message to be a timeout, and treat a hung process more like a crash (and only restart in the latter case).

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


More information about the webkit-unassigned mailing list