RESOLVED WONTFIX 177187
Layout tests plugins/destroy-stream-twice.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=177187
Summary Layout tests plugins/destroy-stream-twice.html is flaky
Matt Lewis
Reported 2017-09-19 13:35:26 PDT
plugins/destroy-stream-twice.html is a flaky timeout on Sierra Release WK2 according to the flakiness dashboard. https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=plugins%2Fdestroy-stream-twice.html On the dashboard, the test has timed out 3 times that can be seen and the timeout has run at least 130s. build: https://build.webkit.org/results/Apple%20Sierra%20Release%20WK2%20(Tests)/r222212%20(4392)/results.html https://build.webkit.org/builders/Apple%20Sierra%20Release%20WK2%20(Tests)/builds/4392 diff: --- /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/plugins/destroy-stream-twice-expected.txt +++ /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/plugins/destroy-stream-twice-actual.txt @@ -1,16 +1,5 @@ -Test for http://bugs.webkit.org/show_bug.cgi?id=13203: REGRESSION: Repro crash in -[WebBaseNetscapePluginView(WebNPPCallbacks) destroyStream:reason:] navigating away from page with DivX movie plug-in +#PID UNRESPONSIVE - com.apple.WebKit.WebContent.Development (pid 58914) +FAIL: Timed out waiting for notifyDone to be called -On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". - - -destroyStream() returns zero to indicate success, or a non-zero error code to indicate failure -PASS document.getElementById('plugin').hasStream is true -PASS document.getElementById('plugin').destroyStream() is 2 -PASS document.getElementById('plugin').destroyStream() is 2 -PASS document.getElementById('plugin').destroyNullStream() is 2 -PASS: You didn't crash. - -PASS successfullyParsed is true - -TEST COMPLETE - +#EOF +#EOF
Attachments
Alexey Proskuryakov
Comment 1 2022-07-01 11:36:13 PDT
Mass closing plug-in bugs, as plug-in support has been removed from WebKit. Please comment and/or reopen if this still affects WebKit in some way.
Note You need to log in before you can comment on or make changes to this bug.