Bug 216538 – [GLIB] webrtc/captureCanvas-webrtc-software-h264-baseline.html is failing since added in r266832

• Component: WebRTC
• Status: NEW

[Diego Pino]

webrtc/captureCanvas-webrtc-software-h264-baseline.html [ Failure ]

Diff: https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r267083%20(15842)/webrtc/captureCanvas-webrtc-software-h264-baseline-diff.txt

--- /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/webrtc/captureCanvas-webrtc-software-h264-baseline-expected.txt
+++ /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/webrtc/captureCanvas-webrtc-software-h264-baseline-actual.txt
@@ -1,4 +1,4 @@
    
 
-PASS captureStream with webrtc - h264 baseline 
+FAIL captureStream with webrtc - h264 baseline promise_test: Unhandled rejection with value: object "IndexSizeError: The index is not in the allowed range."
 

Stderr: https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r267083%20(15842)/webrtc/captureCanvas-webrtc-software-h264-baseline-stderr.txt

(webrtc_video_engine.cc:3160): Absent receive stream; ignoring clearing encoded frame sink for ssrc 0

[Radar WebKit Bug Importer]

<rdar://problem/69368725>

[Lauro Moura]

r285577 updated libwebrtc to M96 and looks like it made this test timeout instead of fail.

stderr:

Mesa: The provided filesystem timestamp for the cache is bogus! Disabling On-disk cache.
(webrtc_video_engine.cc:3482): Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[OpenH264] this = 0x0x7fa2d4000bf0, Warning:Change QP Range from(0,51) to (12,42)
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
[OpenH264] this = 0x0x7fa2d4000bf0, Warning:Actual input framerate 0.000000 is different from framerate in setting 20.000000, suggest to use other rate control modes
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
(decoder_database.cc:131): Failed to initialize decoder.
... (message above repeated a few dozen times)

[Diego Pino]

The test is passing now on GTK but it's very unstable in WPE:

https://results.webkit.org/?suite=layout-tests&test=webrtc%2FcaptureCanvas-webrtc-software-h264-baseline.html&platform=GTK&platform=WPE

https://build.webkit.org/results/WPE-Linux-64-bit-Release-Tests/288000%40main%20%2818816%29/webrtc/captureCanvas-webrtc-software-h264-baseline-diff.txt

--- /home/buildbot/worker/WPE-Linux-64-bit-Release-Tests/build/layout-test-results/webrtc/captureCanvas-webrtc-software-h264-baseline-expected.txt
+++ /home/buildbot/worker/WPE-Linux-64-bit-Release-Tests/build/layout-test-results/webrtc/captureCanvas-webrtc-software-h264-baseline-actual.txt
@@ -1,4 +1,4 @@
 
 
-PASS captureStream with webrtc - h264 baseline
+FAIL captureStream with webrtc - h264 baseline promise_test: Unhandled rejection with value: "test1 failed: tried 200 to get true but got false"