Virtual-clock tests: drain microtasks before a fake fetch charges time
When a test measures async code on a hand-rolled virtual clock (a fake fetch that adds its answer time to a counter instead of using timers), overlapping calls get mis-measured: after call A rejects, queued call B reaches the fake fetch within 1-2 promise jobs and advances the counter before A's rejection has travelled through its async wrappers to the awaiting test, so A appears to take B's time too. Fix: in the fake fetch, await Promise.resolve() in a loop (e.g. 50 times) before adding time, so everything already due settles first. Related gotcha when smoke-testing on real timers: AbortSignal.timeout timers are unref'd, so a fake fetch that only hangs until abort lets Node exit with 'unsettled top-level await' (exit 13); keep the loop alive with a setInterval.