Problems with "wasm-webapi" tests and V8 >= 11.2

[targos]

There seems to be issues with WASM streaming compilation on ARM since V8 11.2.

We had to disable these tests because they are somewhat flaky (sometimes they hang):

• test: skip instantiateStreaming-bad-imports WPT #47292
• test: skip test-wasm-web-api on ARM #47299

[targos]

I cannot reproduce the hang on my M2 mac, but I got this:

$ tools/test.py parallel/test-wasm-web-api --repeat 100 -j 8
=== release test-wasm-web-api ===
Path: parallel/test-wasm-web-api
node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

  Comparison {
    code: 'ERR_WEBASSEMBLY_RESPONSE',
+   message: "WebAssembly response has unsupported MIME type 'text/plain'",
-   message: /^WebAssembly response has status code 418$/,
    name: 'TypeError'
  }
    at async Promise.all (index 1)
    at async /Users/mzasso/git/nodejs/v8-next-update/test/parallel/test-wasm-web-api.js:177:3 {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: TypeError [ERR_WEBASSEMBLY_RESPONSE]: WebAssembly response has unsupported MIME type 'text/plain'
      at new NodeError (node:internal/errors:399:5)
      at node:internal/wasm_web_api:30:13
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    code: 'ERR_WEBASSEMBLY_RESPONSE'
  },
  expected: {
    name: 'TypeError',
    code: 'ERR_WEBASSEMBLY_RESPONSE',
    message: /^WebAssembly response has status code 418$/
  },
  operator: 'rejects'
}

Node.js v20.0.0-pre
Command: out/Release/node /Users/mzasso/git/nodejs/v8-next-update/test/parallel/test-wasm-web-api.js


=== release test-wasm-web-api ===
Path: parallel/test-wasm-web-api
node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

  Comparison {
+   message: 'fetch failed',
-   code: 'ERR_WEBASSEMBLY_RESPONSE',
-   message: "WebAssembly response has unsupported MIME type 'application/wasm;'",
    name: 'TypeError'
  }
    at async Promise.all (index 0)
    at async /Users/mzasso/git/nodejs/v8-next-update/test/parallel/test-wasm-web-api.js:155:3 {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: TypeError: fetch failed
      at Object.fetch (node:internal/deps/undici/undici:11457:11) {
    cause: HTTPParserError: Expected HTTP/
        at Parser.execute (node:internal/deps/undici/undici:9393:19)
        at Parser.readMore (node:internal/deps/undici/undici:9352:16)
        at Socket.onSocketReadable (node:internal/deps/undici/undici:9660:14)
        at Socket.emit (node:events:511:28)
        at emitReadable_ (node:internal/streams/readable:598:12)
        at process.processTicksAndRejections (node:internal/process/task_queues:81:21) {
      code: 'HPE_INVALID_CONSTANT',
      data: '\x00\x00\x00H{"id":2197,"num":0,"params":"AAAAAgAwAAADAAAAAAAAAAACykjJIQ==","type":2}'
    }
  },
  expected: {
    name: 'TypeError',
    code: 'ERR_WEBASSEMBLY_RESPONSE',
    message: "WebAssembly response has unsupported MIME type 'application/wasm;'"
  },
  operator: 'rejects'
}

Node.js v20.0.0-pre
Command: out/Release/node /Users/mzasso/git/nodejs/v8-next-update/test/parallel/test-wasm-web-api.js


[01:07|% 100|+  98|-   2]: Done

Failed tests:
out/Release/node /Users/mzasso/git/nodejs/v8-next-update/test/parallel/test-wasm-web-api.js
out/Release/node /Users/mzasso/git/nodejs/v8-next-update/test/parallel/test-wasm-web-api.js

[targos]

It's not only on ARM: https://ci.nodejs.org/job/node-test-commit-linux-containered/37077/nodes=ubuntu1804_sharedlibs_shared_x64/

[mhdawson]

Failured on windows as well https://ci.nodejs.org/job/node-test-binary-windows-js-suites/20205/RUN_SUBSET=0,nodes=win11-arm64-COMPILED_BY-vs2019-arm64/testReport/junit/(root)/wpt/test_wasm_webapi/

[targos]

There's discussion about this issue in https://bugs.chromium.org/p/v8/issues/detail?id=13902 and it is most likely a problem in Node.js.
/cc @nodejs/cpp-reviewers