[Webkit-unassigned] [Bug 95879] New: NRWT sometimes (maybe?) looks for crash logs for the wrong process

[bugzilla-daemon at webkit.org]

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

           Summary: NRWT sometimes (maybe?) looks for crash logs for the
                    wrong process
           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: timothy_horton at apple.com
                CC: mitz at webkit.org, slewis at apple.com, jberlin at webkit.org,
                    dpranke at chromium.org


Some output from after my logging improvement yesterday (http://trac.webkit.org/changeset/127547):

>From http://build.webkit.org/results/Apple%20MountainLion%20Release%20WK2%20(Tests)/r127606%20(613)/dom/xhtml/level3/core/nodelookupnamespaceuri09-crash-log.txt

> No crash log found for WebKitTestRunner:63827.
>
> stdout:
>
> stderr:
> #CRASHED - WebProcess (pid 63828)

>From http://build.webkit.org/results/Apple%20MountainLion%20Release%20WK2%20(Tests)/r127608%20(614)/fast/scrolling/scrollable-area-overflow-auto-display-none-crash-log.txt

> No crash log found for WebKitTestRunner:68370.
>
> stdout:
> Content-Type: text/plain
> PASS true is true
>
> #EOF
> #EOF
>
> stderr:
> #EOF
> #CRASHED - WebProcess (pid 68371)

Why is NRWT looking for WKTR crash logs instead of WebProcess crash logs, when WKTR clearly told NRWT that it was the WebProcess that crashed?

Or, is there more information that I'm missing here, like that WKTR also crashed *after* printing out the crash message from WebProcess? Is that possible?

Something odd is going on, anyway.

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