Bug 222082

Summary: GPUProcess crashlogs aren't getting attributed to tests
Product: WebKit Reporter: Ryan Haddad <ryanhaddad>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: achristensen, ap, jbedard, webkit-bot-watchers-bugzilla, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: Unspecified   
OS: Unspecified   

Ryan Haddad
Reported 2021-02-17 17:09:11 PST
GPUProcess crashlogs aren't getting attributed to tests, as seen here: https://build.webkit.org/results/Apple-Catalina-Debug-WK2-Tests/r273022%20(208)/results.html
Attachments
Jonathan Bedard
Comment 1 2021-02-18 11:40:10 PST
Not going to be as simple as I initially hoped. About a year ago, Youenn added the appropriate plumbing for attributing GPU processes in https://trac.webkit.org/changeset/254006/webkit. The fact that we aren't attributing crashlogs in the results makes me think that the particular crash is the issue, not GPU process crashes in general. Do we have any details about the nature of the crash? I think Alex was looking into it?
Ryan Haddad
Comment 2 2021-02-18 12:55:02 PST
Ryan Haddad
Comment 3 2021-02-18 12:55:51 PST
(In reply to Ryan Haddad from comment #2) > Here is a different example from today: wrong link, but still applicable I think. https://build.webkit.org/results/Apple-BigSur-Release-WK2-Tests/r273080%20(314)/results.html
Radar WebKit Bug Importer
Comment 4 2021-02-24 17:10:17 PST
Ryan Haddad
Comment 5 2021-03-01 13:13:22 PST
Alexey Proskuryakov
Comment 6 2021-03-01 13:24:00 PST
> The fact that we aren't attributing crashlogs in the results makes me think that the particular crash is the issue, not GPU process crashes in general. Remembering that there were many different crashes all behaving like this, I'm not certain that this is the case.
Note You need to log in before you can comment on or make changes to this bug.