This test is crashing consistently in my system, and I noticed it from a result from run-webkit-tests... but when I run it singly the test runner misses it even though I get a coredump notification in my system every time. $ run-webkit-tests --gtk --debug --force media/encrypted-media/mock-MediaKeySession-update.html Using port 'gtk-wk2' Test configuration: <, x86, debug> Placing test results in /app/webkit/WebKitBuild/Debug/layout-test-results Using Debug build Pixel tests disabled Regular timeout: 30000, slow test timeout: 150000 Command line: /app/webkit/WebKitBuild/Debug/bin/WebKitTestRunner --localhost-alias web-platform.test --localhost-alias www.web-platform.test --localhost-alias www1.web-platform.test --localhost-alias www2.web-platform.test --localhost-alias xn--n8j6ds53lwwkrqhv28a.web-platform.test --localhost-alias xn--lve-6lad.web-platform.test --localhost-alias not-web-platform.test --localhost-alias www.not-web-platform.test --localhost-alias www1.not-web-platform.test --localhost-alias www2.not-web-platform.test --localhost-alias xn--n8j6ds53lwwkrqhv28a.not-web-platform.test --localhost-alias xn--lve-6lad.not-web-platform.test - Found 1 test; running 1, skipping 0. Verbose baseline search path: platform/gtk -> platform/glib -> platform/wk2 -> generic Baseline search path: platform/gtk -> platform/glib -> platform/wk2 -> generic Running 1 test Running 1 WebKitTestRunner. stopping WebKitTestRunner(pid 30) timed out, killing it The test ran as expected.
Odd, this happens way below the default timeout of 30 seconds. And if you set a longer timeout it takes just as long but it even reports it as a pass! $ time run-webkit-tests --gtk --debug --force --time-out-ms=60000 media/encrypted-media/mock-MediaKeySession-update.html [...] Running 1 test Running 1 WebKitTestRunner. The test ran as expected. real 0m6.877s user 0m0.256s sys 0m0.073s
<rdar://problem/107560491>