webrtc/datachannel/datachannel-gc.html is a flaky crash on Catalina and BigSur wk1 Debug. History: https://results.webkit.org/?suite=layout-tests&test=webrtc/datachannel/datachannel-gc.html Results: https://ews-build.s3-us-west-2.amazonaws.com/macOS-Catalina-Debug-WK1-Tests-EWS/r439335-16097-rerun/results.html No crash log found for DumpRenderTree:4986. 07:59:46.557 4872 worker/7 worker/7 webrtc/datachannel/datachannel-gc.html crashed, (no stderr) 07:59:46.558 4872 [55460/55734] webrtc/datachannel/datachannel-gc.html failed unexpectedly (DumpRenderTree crashed [pid=4986]) 07:59:46.558 4872 worker/7 killing driver 07:59:46.575 4872 worker/7 webrtc/datachannel/datachannel-gc.html failed: 07:59:46.575 4872 worker/7 DumpRenderTree crashed [pid=4986]
<rdar://problem/83577903>
Updated test expectations at https://trac.webkit.org/changeset/283124/webkit
Unable to reproduce test results locally on BigSur and I don't have a local platform to test on Catalina.
No crash log found for DumpRenderTree:41375. stdout: PASS Losing local channel reference and closing it on the other side should still allow emitting the close event stderr: 2021-09-22 15:44:57.332 DumpRenderTree[41375:29215309] nil host used in call to allowsSpecificHTTPSCertificateForHost 2021-09-22 15:44:57.332 DumpRenderTree[41375:29215309] nil host used in call to allowsAnyHTTPSCertificateForHost:
07:57:45.393 4872 worker/7 webrtc/datachannel/datachannel-event.html passed 07:57:46.520 4872 worker/7 This test marked as a crash because of no data while reading stdout for the server process. 07:57:46.520 4872 worker/7 This test marked as a crash because of no data while reading stdout for the server process. 07:59:46.557 4872 worker/7 worker/7 webrtc/datachannel/datachannel-gc.html crashed, (no stderr) 07:59:46.558 4872 worker/7 killing driver 07:59:46.575 4872 worker/7 webrtc/datachannel/datachannel-gc.html failed: 07:59:46.575 4872 worker/7 DumpRenderTree crashed [pid=4986]
And here it was 2 minutes without any activity between "marked as a crash" and further output.
*** This bug has been marked as a duplicate of bug 231684 ***