test: skip wasm allocation tests in workers

Refs: #62870
PR-URL: #61898
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>

Author: targos

test/wasm-allocation/test-wasm-allocation-memory64.js

@@ -4,13 +4,19 @@
 // wasm memory64 with guard regions reserves 16GB of virtual address space.
 'use strict';
 
-require('../common');
+const common = require('../common');
 const assert = require('assert');
+const { isMainThread } = require('worker_threads');
 
 // The first allocation should succeed.
 const first = new WebAssembly.Memory({ address: 'i64', initial: 10n, maximum: 100n });
 assert(first);
 
+if (!isMainThread) {
+  // https://github.com/nodejs/node/issues/62870
+  common.skip('Workers terminate instead of throwing');
+}
+
 // Subsequent allocations should eventually fail due to running out of
 // virtual address space. memory64 reserves 16GB per allocation (vs 8GB for
 // memory32), so the limit is reached even faster.

test/wasm-allocation/test-wasm-allocation.js

@@ -4,13 +4,19 @@
 // wasm memory32 with guard regions reserves 8GB of virtual address space.
 'use strict';
 
-require('../common');
+const common = require('../common');
 const assert = require('assert');
+const { isMainThread } = require('worker_threads');
 
 // The first allocation should succeed.
 const first = new WebAssembly.Memory({ initial: 10, maximum: 100 });
 assert(first);
 
+if (!isMainThread) {
+  // https://github.com/nodejs/node/issues/62870
+  common.skip('Workers terminate instead of throwing');
+}
+
 // Subsequent allocations should eventually fail due to running out of
 // virtual address space.
 assert.throws(() => {