Bug 207046 - [ macOS ] imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/seeking/seek-to-currentTime.html is flaky failing
Summary: [ macOS ] imported/w3c/web-platform-tests/html/semantics/embedded-content/med...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Keywords: InRadar
Depends on:
Reported: 2020-01-31 08:11 PST by Jacob Uphoff
Modified: 2020-02-13 11:44 PST (History)
3 users (show)

See Also:

Update Test Expectations (1.79 KB, patch)
2020-01-31 08:17 PST, Jacob Uphoff
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jacob Uphoff 2020-01-31 08:11:01 PST

This test is flak failing for all visible history

It has failed consistently on the Catalina gpuproccess debug bot

I was unable to reproduce in iteration runs



--- /Volumes/Data/slave/catalina-debug-tests-wk2-gpuprocess/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/seeking/seek-to-currentTime-expected.txt
+++ /Volumes/Data/slave/catalina-debug-tests-wk2-gpuprocess/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/embedded-content/media-elements/seeking/seek-to-currentTime-actual.txt
@@ -1,3 +1,5 @@
-FAIL seek to currentTime assert_greater_than: seekable ranges expected a number greater than 0 but got 0
+Harness Error (TIMEOUT), message = null
+TIMEOUT seek to currentTime Test timed out
Comment 1 Radar WebKit Bug Importer 2020-01-31 08:11:29 PST
Comment 2 Jacob Uphoff 2020-01-31 08:17:38 PST
Created attachment 389351 [details]
Update Test Expectations
Comment 3 Truitt Savell 2020-01-31 08:33:04 PST
Comment on attachment 389351 [details]
Update Test Expectations

Clearing flags on attachment: 389351

Committed r255497: <https://trac.webkit.org/changeset/255497>
Comment 4 Alexey Proskuryakov 2020-01-31 21:51:12 PST
The GPU process bot is WebKit2, so consistent failures there wouldn't be tracked by this bug. Also, it has a different failure.
Comment 5 Jacob Uphoff 2020-02-13 11:44:46 PST
Updated test expectations: https://trac.webkit.org/changeset/256529/webkit