Bug 198103 - imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/offsets-into-the-media-resource/currentTime.html is flaky
Summary: imported/w3c/web-platform-tests/html/semantics/embedded-content/media-element...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-22 02:03 PDT by Alicia Boya García
Modified: 2019-05-22 02:03 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alicia Boya García 2019-05-22 02:03:30 PDT 
It usually passes, but sometimes it doesn't:

  var v = document.createElement('video');
  assert_equals(v.readyState, v.HAVE_NOTHING);
  v.currentTime = Number.MAX_VALUE;
  assert_equals(v.currentTime, Number.MAX_VALUE);

--- /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/offsets-into-the-media-resource/currentTime-expected.txt
+++ /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/offsets-into-the-media-resource/currentTime-actual.txt
@@ -1,5 +1,7 @@
+
+Harness Error (TIMEOUT), message = null
 
 PASS currentTime initial value 
 FAIL setting currentTime when readyState is HAVE_NOTHING assert_equals: expected 1.7976931348623157e+308 but got 0
-PASS setting currentTime when readyState is greater than HAVE_NOTHING 
+TIMEOUT setting currentTime when readyState is greater than HAVE_NOTHING Test timed out