Repository navigation
Problems with "wasm-webapi" tests and V8 >= 11.2 #47297
Copy link
Copy link
Closed
Labels
armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.wasmIssues and PRs related to WebAssembly.Issues and PRs related to WebAssembly.
Description
Activity
- addedv8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.wasmIssues and PRs related to WebAssembly.Issues and PRs related to WebAssembly.
on Mar 29, 2023 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- changed the title
[-]Problems with "wasm-webapi" tests on ARM and V8 >= 11.2[/-][+]Problems with "wasm-webapi" tests and V8 >= 11.2[/+]on Apr 4, 2023 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-reviewers285 remaining items
Load more actions- added 2 commits that reference this issue
on Apr 15, 2024 - added a commit that references this issue
on Apr 16, 2024 - added a commit that references this issue
on Apr 17, 2024 - added a commit that references this issue
on Apr 18, 2024 - added a commit that references this issue
on Apr 19, 2024 I think this is fixed.
Metadata
Metadata
Assignees
Labels
armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.wasmIssues and PRs related to WebAssembly.Issues and PRs related to WebAssembly.
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):