wasm.yaml/wasm/references/multitable.js.wasm-collect-continuously is a flaky failure on Catalina Release. HISTORY: https://results.webkit.org/?suite=javascriptcore-tests&test=wasm.yaml%2Fwasm%2Freferences%2Fmultitable.js.wasm-collect-continuously https://build.webkit.org/#/builders/4/builds/3520 FAILURE: wasm.yaml/wasm/references/multitable.js.wasm-collect-continuously: Timed out after 587.000000 sec seconds! wasm.yaml/wasm/references/multitable.js.wasm-collect-continuously: test_script_78919: line 2: 4473 Trace/BPT trap: 5 ( "$@" ../../../../.vm/JavaScriptCore.framework/Helpers/jsc --useFTLJIT\=false --useFunctionDotArguments\=true --validateExceptionChecks\=true --useDollarVM\=true --maxPerThreadStackUsage\=1572864 -m --collectContinuously\=true --verifyGC\=true --useFTLJIT\=true multitable.js ) wasm.yaml/wasm/references/multitable.js.wasm-collect-continuously: ERROR: Unexpected exit code: 133 FAIL: wasm.yaml/wasm/references/multitable.js.wasm-collect-continuously
<rdar://problem/82739971>
It appears to have been flaky about a month after the test started running on that queue with the first failure occurring at r274256.
Created attachment 437898 [details] Patch
Comment on attachment 437898 [details] Patch r=me
armv7 skips this test, so the bot failure is unrelated
Committed r282300 (241573@main): <https://commits.webkit.org/241573@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 437898 [details].