Bug 198103
Summary: | imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/offsets-into-the-media-resource/currentTime.html is flaky | ||
---|---|---|---|
Product: | WebKit | Reporter: | Alicia Boya García <aboya> |
Component: | Media | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | ||
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Alicia Boya García
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
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |