[Webkit-unassigned] [Bug 66806] New: [chromium] Stacktrace not in test output when a test crashes

[bugzilla-daemon at webkit.org]

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

           Summary: [chromium] Stacktrace not in test output when a test
                    crashes
           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: jamesr at chromium.org
                CC: eric at webkit.org, abarth at webkit.org,
                    dglazkov at chromium.org, dpranke at chromium.org


When a test crashes in the chromium port, the full stacktrace is produced by the binary but isn't actually visible it the output.  It looks like the output is ending up in DriverOutput.text, but when a test crashes we only output DriverOutput.error.  http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/layout_tests/layout_package/test_result_writer.py#L69.  I think this is due to http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/layout_tests/port/chromium.py#L448 which pipes stderr to the same place as stdout.

If locally I patch http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/layout_tests/layout_package/test_result_writer.py#L69 to write "driver_output.error + driver_output.text", then I do see the full stack (in addition to whatever test output was produced on stdout).  Based on the comments we should be using ServerProcess, which does have logic to open up stdout and stderr FDs and select() between them.

Because of this bug we often don't get usable stack traces from even the debug layout test bots, which sucks.

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