Chris Tate e73dbe0bb3 Run the three.js nodes fixture unsanitized in the sanitized lane ...

The sanitized nodes build compiles one 1.14 GB LLVM module, and its clang
compile peaks at about 16 GB, more than the CI runners have, so the
fixture failed in every san shard that ran it. It now builds without the
sanitizer there, as in the plain lane; every other three.js fixture keeps
it. The fixture goes back under the sanitizer once sanitized dev builds
compile large programs in shards.

2026-10-24 20:41:45 -05:00

..

corpus

Iterate classes with object-literal iterators and close them on early exits (#1860)

2026-10-24 20:30:36 -05:00

coverage-fixtures

Compile more npm and CommonJS JavaScript dependencies statically (#2122)

2026-10-24 18:30:56 -05:00

deadstrip

…

diagnostics

Compile more npm and CommonJS JavaScript dependencies statically (#2122)

2026-10-24 18:30:56 -05:00

ffi

…

fixtures

Check with a tsc-ts server shared by later builds (opt-in) (#2153)

2026-10-24 19:12:05 -05:00

harness

Run the three.js nodes fixture unsanitized in the sanitized lane

2026-10-24 20:41:45 -05:00

library-mode

Cache untyped property access in programs that declare classes (reland)

2026-10-24 08:22:30 -05:00

node-parallel

Compare termination signals and resolve the Node checkout path in the test/parallel runner

2026-10-24 16:00:06 -05:00

test262

Convert compareArray's message only when the arrays differ

2026-10-24 16:16:23 -05:00

wasm-spec

Merge main

2026-10-20 17:56:44 -05:00