Chris Tate 577f086658 Space the timer delays in two order-sensitive tests and raise the static-spatial timeout ...

mock-timers' "named and namespace imports keep the loop's timers" and
6811-node-island-uncaught-listener check the order in which real timers
fire, with delays 1 to 5 ms apart that are scheduled one after another.
On a busy runner more time than that can pass between scheduling two of
them, and the order flips in either lane: the sanitized node:test run saw
Node's reference print 'named promise' first, and the sanitized
llvm-differential run saw 'island timer 1' before 'native timer after'.
The delays are now 100 ms apart in mock-timers (100, 200, 300) and the
island's timers (150, 250) start 100 ms after the native ones (10, 50).
Node prints the same output as before.

static-spatial bundles three.js and builds it with the sanitizer, which
passed the default 300 s test timeout on a busy runner. Its cases take
three.test.ts's 1200 s timeout.

2026-10-28 12:49:21 -05:00

..

cases

Space the timer delays in two order-sensitive tests and raise the static-spatial timeout

2026-10-28 12:49:21 -05:00

update

Add t.assert.snapshot and t.assert.fileSnapshot

2026-10-18 05:31:40 -05:00