Bug 218010

Summary: [GStreamer] Several audioworklet tests are flaky
Product: WebKit Reporter: Diego Pino <dpino>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: clopez, lmoura
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=219603
https://bugs.webkit.org/show_bug.cgi?id=218370

Description Diego Pino 2020-10-21 01:08:40 PDT
The following tests have reported flaky failures in GTK:

  imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletnode-output-channel-count.https.html
  imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletprocessor-process-zero-outputs.https.html
  imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/suspended-context-messageport.https.html
  imported/w3c/web-platform-tests/webaudio/the-audio-api/the-convolvernode-interface/active-processing.https.html

Diff: https://build.webkit.org/results/GTK-Linux-64-bit-Release-Tests/r268786%20(16549)/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-convolvernode-interface/active-processing.https-diff.txt

--- /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-convolvernode-interface/active-processing.https-expected.txt
+++ /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-convolvernode-interface/active-processing.https-actual.txt
@@ -1,14 +1,12 @@
+
+Harness Error (TIMEOUT), message = null
 
 PASS # AUDIT TASK RUNNER STARTED.
 PASS Executing "initialize"
-PASS Executing "test"
-PASS Audit report
+TIMEOUT Executing "test" Test timed out
+NOTRUN Audit report
 PASS > [initialize]
 PASS   AudioWorklet module loading resolved correctly.
 PASS < [initialize] All assertions passed. (total 1 assertions)
 PASS > [test]
-PASS   Test 0: Number of convolver output channels is equal to 2.
-FAIL X Number of distinct values is not equal to 2. Got 1. assert_true: expected true got false
-FAIL < [test] 1 out of 2 assertions were failed. assert_true: expected true got false
-FAIL # AUDIT TASK RUNNER FINISHED: 1 out of 2 tasks were failed. assert_true: expected true got false
 
Diff: https://build.webkit.org/results/GTK-Linux-64-bit-Release-Tests/r268786%20(16549)/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletnode-output-channel-count.https-diff.txt

--- /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletnode-output-channel-count.https-expected.txt
+++ /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletnode-output-channel-count.https-actual.txt
@@ -1,13 +1,9 @@
+
+Harness Error (TIMEOUT), message = null
 
 PASS # AUDIT TASK RUNNER STARTED.
-PASS Executing "Dynamically change the channel count to if unspecified."
-PASS Executing "Givien outputChannelCount must be honored."
-PASS Audit report
+TIMEOUT Executing "Dynamically change the channel count to if unspecified." Test timed out
+NOTRUN Executing "Givien outputChannelCount must be honored."
+NOTRUN Audit report
 PASS > [Dynamically change the channel count to if unspecified.]
-PASS   The expected output channel count is equal to 17.
-PASS < [Dynamically change the channel count to if unspecified.] All assertions passed. (total 1 assertions)
-PASS > [Givien outputChannelCount must be honored.]
-PASS   The expected output channel count is equal to 2.
-PASS < [Givien outputChannelCount must be honored.] All assertions passed. (total 1 assertions)
-PASS # AUDIT TASK RUNNER FINISHED: 2 tasks ran successfully.
 
Diff: https://build.webkit.org/results/GTK-Linux-64-bit-Release-Tests/r268786%20(16549)/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletprocessor-process-zero-outputs.https-diff.txt

--- /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletprocessor-process-zero-outputs.https-expected.txt
+++ /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/audioworkletprocessor-process-zero-outputs.https-actual.txt
@@ -1,9 +1,8 @@
+
+Harness Error (TIMEOUT), message = null
 
 PASS # AUDIT TASK RUNNER STARTED.
-PASS Executing "check-zero-outputs"
-PASS Audit report
+TIMEOUT Executing "check-zero-outputs" Test timed out
+NOTRUN Audit report
 PASS > [check-zero-outputs]
-PASS   |outputs| has been all zeros for 1 seconds as expected. is true.
-PASS < [check-zero-outputs] All assertions passed. (total 1 assertions)
-PASS # AUDIT TASK RUNNER FINISHED: 1 tasks ran successfully.
 
Diff: https://build.webkit.org/results/GTK-Linux-64-bit-Release-Tests/r268786%20(16549)/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/suspended-context-messageport.https-diff.txt

--- /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/suspended-context-messageport.https-expected.txt
+++ /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/webaudio/the-audio-api/the-audioworklet-interface/suspended-context-messageport.https-actual.txt
@@ -1,5 +1,5 @@
 
-PASS realtime suspended
+FAIL realtime suspended assert_equals: created message time expected 0.03192743764172336 but got 0.034829931972789115
 PASS offline before start
 PASS offline on complete
Comment 1 Philippe Normand 2020-10-29 02:14:46 PDT
*** Bug 218321 has been marked as a duplicate of this bug. ***
Comment 2 Lauro Moura 2020-12-07 10:29:30 PST
I've just opened bug219603 about a similar message for the ChannelMergerNode.

Should each node type be kept separate or should we group them here as this looks like a harness issue?