trending/scriptc
1
0
Fork 0
mirror of https://github.com/vercel-labs/scriptc.git synced 2026-11-02 07:43:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
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.
This commit is contained in:
Chris Tate
2026-10-24 20:41:45 -05:00
parent 03af6fb9ff
commit e73dbe0bb3
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/harness/three.test.ts
+5 -1
View File
@@ -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;