It looks like the imported/w3c/web-platform-tests/wasm/jsapi/interface.any.worker.html added in https://trac.webkit.org/changeset/247457/webkit is flaky on Mac Debug. History: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2Fwasm%2Fjsapi%2Finterface.any.worker.html Diff: --- /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/wasm/jsapi/interface.any.worker-expected.txt +++ /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/wasm/jsapi/interface.any.worker-actual.txt @@ -1,5 +1,3 @@ -CONSOLE MESSAGE: line 1774: TypeError: null is not an object (evaluating 'this.message_target.removeEventListener') -CONSOLE MESSAGE: line 154: TypeError: undefined is not an object (evaluating 'WebAssembly.Global.prototype') Harness Error (FAIL), message = TypeError: undefined is not an object (evaluating 'WebAssembly.Global.prototype')
<rdar://problem/53686304>
This is imported from wpt, and the error related to `WebAssembly.Global` thing is expected since this is not implemented yet. We can mark it as flaky. When `WebAssembly.Global` is implemented, we can make it PASS.
Marked test as flakey in https://trac.webkit.org/changeset/248005/webkit
Curious why an unimplemented feature causes flaky failures, not 100% failures. Is this test racy in some way?
Let's unmark it since I implemented WebAssembly.Global.
Created attachment 384792 [details] Patch
Comment on attachment 384792 [details] Patch Clearing flags on attachment: 384792 Committed r253119: <https://trac.webkit.org/changeset/253119>
All reviewed patches have been landed. Closing bug.