Bug 210417

Summary:	[WPE][EME] Some clearkey tests are failing
Product:	WebKit	Reporter:	Lauro Moura <lmoura>
Component:	WPE WebKit	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	bugs-noreply, cturner
Priority:	P2
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

Description Lauro Moura 2020-04-12 20:31:11 PDT

They were marked as Crashing from r207741, but after r259865-r259866 are just failing.

* imported/w3c/web-platform-tests/encrypted-media/clearkey-keystatuses.https.html - No error until r256429-r256430 (first crash)

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/encrypted-media/clearkey-keystatuses.https-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/encrypted-media/clearkey-keystatuses.https-actual.txt
@@ -1,3 +1,3 @@
 
-PASS org.w3.clearkey, temporary, keystatuses 
+FAIL org.w3.clearkey, temporary, keystatuses assert_in_array: keystatuses should have the two expected keys with keystatus 'usable' or 'status-pending' value "[{\"key\":\"0xad13f9ea2be698b875f504a8e3ccea64\",\"value\":\"usable\"},{\"key\":\"0x558ee541b90ab2f3950d00ade3760d45\",\"value\":\"usable\"}]" not in array ["[{\"key\":\"0x558ee541b90ab2f3950d00ade3760d45\",\"value\":\"usable\"},{\"key\":\"0xad13f9ea2be698b875f504a8e3ccea64\",\"value\":\"usable\"}]", "[{\"key\":\"0x558ee541b90ab2f3950d00ade3760d45\",\"value\":\"status-pending\"},{\"key\":\"0xad13f9ea2be698b875f504a8e3ccea64\",\"value\":\"status-pending\"}]"]
 
* imported/w3c/web-platform-tests/encrypted-media/clearkey-mp4-playback-temporary-multikey-sequential-readyState.https.html - Already marked as a failure before. The last pass was r232343.

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/encrypted-media/clearkey-mp4-playback-temporary-multikey-sequential.https-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/encrypted-media/clearkey-mp4-playback-temporary-multikey-sequential.https-actual.txt
@@ -1,3 +1,3 @@
 
-Pass	org.w3.clearkey, successful playback, temporary, mp4, multiple keys, sequential 
+FAIL org.w3.clearkey, successful playback, temporary, mp4, multiple keys, sequential assert_equals: It should require all keys to reach end of content expected 2 but got 1
 

* imported/w3c/web-platform-tests/encrypted-media/clearkey-mp4-playback-temporary-multikey-sequential.https.html - Already marked as a failure before. The last pass was r232343.

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/async_005-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/async_005-actual.txt
@@ -1,3 +1,3 @@
 
-FAIL A script element with both async and defer set should execute asynchronously assert_equals: expected "2134" but got "2341"
-2341
+PASS A script element with both async and defer set should execute asynchronously 
+2134

Comment 1 Charlie Turner 2020-05-04 06:43:49 PDT

imported/w3c/web-platform-tests/encrypted-media/clearkey-keystatuses.https.html has been recently fixed.

imported/w3c/web-platform-tests/encrypted-media/clearkey-mp4-playback-temporary-multikey-sequential-readyState.https.html I triaged as inherently flakey. https://bugs.webkit.org/show_bug.cgi?id=210965

imported/w3c/web-platform-tests/encrypted-media/clearkey-mp4-playback-temporary-multikey-sequential.https.html

You have quoted a text diff from an unrelated test, this test is passing for me locally.

Comment 2 Charlie Turner 2020-05-04 06:45:00 PDT

By the way, until https://bugs.webkit.org/show_bug.cgi?id=211183 lands, it's going to be hard to keep the expectations consistent. EME is GTK/WPE-agnostic, so I am hoping to update all this in the common glib expectation when I can.