[Webkit-unassigned] [Bug 74039] New: chromium win test bots can get stuck

[bugzilla-daemon at webkit.org]

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

           Summary: chromium win test bots can get stuck
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: dpranke at chromium.org
                CC: eric at webkit.org, tony at chromium.org, abarth at webkit.org,
                    dpranke at chromium.org, simonjam at chromium.org,
                    scheib at chromium.org


It appears there are cases where the Chromium win test bots can get stuck or wedged still (see, e.g.: http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Vista/builds/9519/steps/webkit_tests/logs/stdio). This can be very disruptive to gardeners and others watching the bots.

What seems to be happening is that DRT crashes, but instead of exiting, a dialog gets displayed on the bot. Because the chromium port-specific implementation on the Port class relies on DRT to enforce the timeout and exit, the worker thread in NRWT hangs indefinitely instead of timing out. We should fix this :)

At one point we also had code to detect when these threads were wedged, but that was removed (in r90207). We should consider restoring that code, perhaps just temporarily, if fixing this properly turns out to be hard.

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