Revert "test: ensure message event fires in worker message port test"

This reverts commit 9790315e15.

Refs: https://github.com/nodejs/node/pull/59952
PR-URL: https://github.com/nodejs/node/pull/60126
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
This commit is contained in:
Luigi Pinca 2025-10-13 08:48:18 +02:00 committed by GitHub
parent 1cd16e5355
commit 985e2fb383
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -27,14 +27,3 @@ port2.postMessage(0);
// This is part of the test -- the event loop should be available and not stall // This is part of the test -- the event loop should be available and not stall
// out due to the recursive .postMessage() calls. // out due to the recursive .postMessage() calls.
setTimeout(common.mustCall(), 0); setTimeout(common.mustCall(), 0);
// Assert that the 'message' handler was actually called.
//
// We do not want to assert a specific call count, so common.mustCall cannot be
// used in the port1.on('message' callback directly.
process.once(
'beforeExit',
common.mustCall(() => {
assert(count > 0, 'count should be greater than 0');
})
);