NEW 198081
[Mac] Layout Test imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/track/track-element/track-remove-track.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=198081
Summary [Mac] Layout Test imported/w3c/web-platform-tests/html/semantics/embedded-con...
Shawn Roberts
Reported 2019-05-21 13:08:20 PDT
The following layout test is failing on Mac Release and Debug WK1 and WK2 imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/track/track-element/track-remove-track.html Probable cause: Test appears to have been flaky for a very long time. Dashboard shows flaky failures on every queue for Debug runs and Release WK1. Release runs for WK2 are showing up recently, but local testing shows the same Harness Error (TIMEOUT) for all Mac test platforms Reproduced with the old revision I could spade. run-webkit-tests imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/track/track-element/track-remove-track.html --iter 100 -f -1 Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2Fhtml%2Fsemantics%2Fembedded-content%2Fmedia-elements%2Ftrack%2Ftrack-element%2Ftrack-remove-track.html Diff: --- /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/track/track-element/track-remove-track-expected.txt +++ /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/track/track-element/track-remove-track-actual.txt @@ -1,3 +1,5 @@ -PASS Tests that the 'removetrack' event is fired when an out-of-band TextTrack is removed. +Harness Error (TIMEOUT), message = null +TIMEOUT Tests that the 'removetrack' event is fired when an out-of-band TextTrack is removed. Test timed out +
Attachments
Radar WebKit Bug Importer
Comment 1 2019-05-21 13:08:48 PDT
Note You need to log in before you can comment on or make changes to this bug.