[Webkit-unassigned] [Bug 63981] New: new-run-webkit-tests does not correctly identify timeouts on Mac

[bugzilla-daemon at webkit.org]

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

           Summary: new-run-webkit-tests does not correctly identify
                    timeouts on Mac
           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: eric at webkit.org
                CC: abarth at webkit.org, ojan at chromium.org,
                    dpranke at chromium.org
            Blocks: 34984


new-run-webkit-tests does not correctly identify timeouts on Mac

Example:
2011-07-06 01:55:41,276 43149 printing.py:470 INFO 10 slowest tests that are not marked as SLOW and did not timeout/crash:
2011-07-06 01:55:41,276 43149 printing.py:470 INFO   fast/workers/storage/interrupt-database.html took 30.0 seconds
2011-07-06 01:55:41,276 43149 printing.py:470 INFO   fast/workers/worker-close-more.html took 30.0 seconds
2011-07-06 01:55:41,276 43149 printing.py:470 INFO   fast/workers/shared-worker-frame-lifecycle.html took 30.0 seconds
2011-07-06 01:55:41,276 43149 printing.py:470 INFO   fast/workers/shared-worker-lifecycle.html took 30.0 seconds
2011-07-06 01:55:41,276 43149 printing.py:470 INFO   fast/workers/worker-lifecycle.html took 30.0 seconds

What's happening is that we're not reading stderr correctly in ServerProcess, so we never see the timeout notification.

At least I think that's what's happening.

I believe this to be very related to bug 63683.  Which is about listening for #CRASHED correctly on stderr.

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