Bug 240830

Summary: REGRESSION (ANGLE update to 2022-04-26?): [ Monterey wk2 ] webgl/2.0.0/conformance/attribs/gl-vertexattribpointer-offsets.html is a flaky timeout
Product: WebKit Reporter: Karl Rackler <rackler>
Component: WebGLAssignee: Karl Rackler <rackler>
Status: NEW    
Severity: Normal CC: dino, gman, kbr, kkinnunen, kpiddington, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=242106
https://bugs.webkit.org/show_bug.cgi?id=253960
Bug Depends on: 239114    
Bug Blocks:    

Attachments
Radar WebKit Bug Importer
Comment 1 2022-05-23 15:01:02 PDT
Karl Rackler
Comment 2 2022-05-23 15:08:48 PDT
I have marked this test as a flaky timeout while this issue is investigated.
Karl Rackler
Comment 3 2022-05-23 15:12:18 PDT
EWS
Comment 4 2022-05-23 15:15:16 PDT
Test gardening commit r294687 (250893@main): <https://commits.webkit.org/250893@main> Reviewed commits have been landed. Closing PR #946 and removing active labels.
Ryan Haddad
Comment 5 2022-05-25 11:08:17 PDT
The test had been running in 19 seconds or fewer up until the result at 250045@main, then it started taking https://commits.webkit.org/250044@main was a update of ANGLE, so it is likely the cause of the slowdown.
Kenneth Russell
Comment 6 2022-05-25 11:30:39 PDT
This test runs pretty much instantaneously on macOS 12.4 on an M1 MBP in both Safari Tech Preview and Chrome Canary, both with ANGLE's Metal backend. What could be the essential difference between WebKit's layout test harness and the browser causing this test to be so slow?
Ryan Haddad
Comment 7 2022-05-25 11:33:07 PDT
(In reply to Ryan Haddad from comment #5) > The test had been running in 19 seconds or fewer up until the result at > 250045@main, then it started taking (sorry, saved before finishing my sentence) ... then it started taking 20+ seconds and intermittently timing out. (In reply to Kenneth Russell from comment #6) at could be the essential difference between WebKit's layout test harness > and the browser causing this test to be so slow? This I'm not sure, maybe Kimmo or others can comment.
Note You need to log in before you can comment on or make changes to this bug.