Bug 179827

Summary: Layout Test inspector/canvas/shaderProgram-add-remove-webgl2.html is flaky
Product: WebKit Reporter: Matt Lewis <jlewis3>
Component: New BugsAssignee: ayumi_kojima
Status: NEW    
Severity: Normal CC: ayumi_kojima, hi, jenner, joepeck
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=174066
https://bugs.webkit.org/show_bug.cgi?id=228934
Attachments:
Description Flags
Patch jenner: commit-queue-

Matt Lewis
Reported 2017-11-17 10:15:44 PST
inspector/canvas/shaderProgram-add-remove-webgl2.html is a flaky timeout and failure on all macOS platforms according to the dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=inspector%2Fcanvas%2FshaderProgram-add-remove-webgl2.html The test was previously marked as a flaky timeout but it seems to also be a flaky failure as well. and it does not seem to be a recent regression. The previous bug: https://bugs.webkit.org/show_bug.cgi?id=174066 is where the test was marked as a flaky timeout. current failing test results: https://build.webkit.org/results/Apple%20Sierra%20Debug%20WK2%20(Tests)/r224961%20(4057)/results.html Diff: --- /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/inspector/canvas/shaderProgram-add-remove-webgl2-expected.txt +++ /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/inspector/canvas/shaderProgram-add-remove-webgl2-actual.txt @@ -16,5 +16,4 @@ -- Running test case: Canvas.ShaderProgram.webgl2.ParentCanvasRemoved PASS: Removed ShaderProgram. PASS: ShaderProgram should have a parent Canvas. -PASS: Removed ShaderProgram before Canvas.
Attachments
Patch (1.70 KB, patch)
2021-07-07 18:14 PDT, ayumi_kojima
jenner: commit-queue-
ayumi_kojima
Comment 1 2021-07-07 18:14:24 PDT
Robert Jenner
Comment 2 2021-07-07 18:33:33 PDT
(In reply to ayumi_kojima from comment #1) > Created attachment 433104 [details] > Patch Added to the wrong bug.
Note You need to log in before you can comment on or make changes to this bug.