test: replace flaky immediates event loop test

Replace a flaky immediates event loop test that hasn't truly made sense for a while, since it has gone through so many different iterations, with a new test that is verifying the same behavior but without so much potential for flakiness. Fixes: #24497
nodejs · apapirovski · Jan 7, 2022 · Jan 7, 2022 · 8f73f2b71775c072ca1a5afa4b58fb53197dfe60
commit 8f73f2b71775c072ca1a5afa4b58fb53197dfe60
diff --git a/test/parallel/parallel.status b/test/parallel/parallel.status
@@ -9,8 +9,6 @@ prefix parallel
 test-repl-sigint-nested-eval: PASS, FLAKY
 
 [$system==win32]
-# https://github.com/nodejs/node/issues/24497
-test-timers-immediate-queue: PASS,FLAKY
 # https://github.com/nodejs/node/issues/23277
 test-worker-memory: PASS,FLAKY
 # https://github.com/nodejs/node/issues/41206

diff --git a/test/parallel/test-timers-immediate-event-loop.js b/test/parallel/test-timers-immediate-event-loop.js
@@ -0,0 +1,34 @@
+// Flags: --expose-internals
+'use strict';
+
+const common = require('../common');
+
+const assert = require('assert');
+const { sleep } = require('internal/util');
+
+// SetImmediate should clear its existing queue on each event loop run
+// but leave any newly scheduled Immediates until the next run.
+//
+// Since timer expiries are notoriously flaky and dependant on specific
+// OS configurations, we instead just check that an Immediate queue
+// will eventually be interrupted by the timer — regardless of how long
+// it actually takes for that to happen.
+
+const duration = 1;
+let nextImmediate;
+
+const exit = common.mustCall(() => {
+  assert.ok(nextImmediate.hasRef());
+  process.exit();
+});
+
+function check() {
+  sleep(duration);
+  nextImmediate = setImmediate(check);
+}
+
+setImmediate(common.mustCall(() => {
+  setTimeout(exit, duration);
+
+  check();
+}));
diff --git a/test/parallel/test-timers-immediate-queue.js b/test/parallel/test-timers-immediate-queue.js