Bug 184614 - Layout Test media/W3C/audio/events/event_order_loadstart_progress.html is a flaky failure
Summary: Layout Test media/W3C/audio/events/event_order_loadstart_progress.html is a f...
Status: RESOLVED DUPLICATE of bug 181966
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-13 17:23 PDT by Ryan Haddad
Modified: 2019-10-11 23:32 PDT (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2018-04-13 17:23:47 PDT
The following layout test is flaky on iOS and macOS Debug.

media/W3C/audio/events/event_order_loadstart_progress.html

Probable cause:

Unknown.

Flakiness Dashboard:

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=media%2FW3C%2Faudio%2Fevents%2Fevent_order_loadstart_progress.html

--- /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/media/W3C/audio/events/event_order_loadstart_progress-expected.txt
+++ /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/media/W3C/audio/events/event_order_loadstart_progress-actual.txt
@@ -6,6 +6,9 @@
 PASS true is true
 
 TEST COMPLETE
+PASS true is true
+
+TEST COMPLETE
 spec reference
Comment 1 Ryan Haddad 2018-11-06 10:14:39 PST
This is still happening.
Comment 2 Shawn Roberts 2019-01-29 10:11:00 PST
Test is no longer affecting iOS Debug, but is still affecting MacOS Debug.

media/W3C/audio/events/event_order_loadstart_progress.html

Flakiness Dashboard:

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=media%2FW3C%2Faudio%2Fevents%2Fevent_order_loadstart_progress.html

Reproduced with: 

rwt --root d240657 media/W3C/audio/events/event_order_loadstart_progress.html --iterations 500 -f --debug

Diff is the same.
Comment 3 Peng Liu 2019-10-11 23:32:35 PDT

*** This bug has been marked as a duplicate of bug 181966 ***