From d10b98b8273ef35b001e8cf9f0a539ffd4fafd21 Mon Sep 17 00:00:00 2001 From: Luigi Pinca Date: Sun, 5 Oct 2025 18:08:12 +0200 Subject: [PATCH] Revert "test: ensure message event fires in worker message port test" This reverts commit 9790315e158a0560932595ff9df9c598e1c2c285. Refs: https://github.com/nodejs/node/pull/59952 --- .../test-worker-message-port-infinite-message-loop.js | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/test/parallel/test-worker-message-port-infinite-message-loop.js b/test/parallel/test-worker-message-port-infinite-message-loop.js index 88820ac8918476..0cd1cc06802055 100644 --- a/test/parallel/test-worker-message-port-infinite-message-loop.js +++ b/test/parallel/test-worker-message-port-infinite-message-loop.js @@ -27,14 +27,3 @@ port2.postMessage(0); // This is part of the test -- the event loop should be available and not stall // out due to the recursive .postMessage() calls. 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'); - }) -);