From e73dbe0bb3842e18d793600a449a9b3ae62c8d40 Mon Sep 17 00:00:00 2001 From: Chris Tate Date: Sat, 24 Oct 2026 20:41:45 -0500 Subject: [PATCH] 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. --- tests/harness/three.test.ts | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tests/harness/three.test.ts b/tests/harness/three.test.ts index 27fb86d1f..967c8654a 100644 --- a/tests/harness/three.test.ts +++ b/tests/harness/three.test.ts @@ -72,7 +72,11 @@ test.for(cases)( const previousTarget = process.env["SCRIPTC_TARGET"]; const previousCc = process.env["SCRIPTC_CC"]; const wasm = target === "wasm32-wasi"; - const sanitize = !wasm && process.env["SCRIPTC_SAN"] === "1"; + // The sanitized nodes program is one 1.14 GB LLVM module, whose clang + // compile needs about 16 GB, more than the CI runners have. It runs + // unsanitized until sanitized dev builds compile large programs in + // shards; every other fixture keeps the sanitizer. + const sanitize = !wasm && fixture !== "nodes" && process.env["SCRIPTC_SAN"] === "1"; try { if (wasm) { process.env["SCRIPTC_TARGET"] = target;