From 1d25cdb4ad519a0aa5000bd14094ba8fbe5e4634 Mon Sep 17 00:00:00 2001 From: Michael Johnston Date: Mon, 5 Oct 2026 20:43:34 -0700 Subject: [PATCH] test(lastcode): read CLI errors from both output streams SQLite warnings can occupy stderr while the decode error is on stdout. Check both streams so the reconciliation regression stays meaningful under the package builder's Node runtime. Carry-Group: build-ci Carry-Fix: Local package reconciliation diagnostic regression Carry-Observation: A Node 24 SQLite warning must not hide a decode error written to stdout from the regression assertion. --- apps/server/src/cli/project.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/server/src/cli/project.test.ts b/apps/server/src/cli/project.test.ts index f2af62ecc49a..ea9a496552dd 100644 --- a/apps/server/src/cli/project.test.ts +++ b/apps/server/src/cli/project.test.ts @@ -104,7 +104,7 @@ it("keeps reconciliation JSON on stdout and migration diagnostics on stderr", () NodeFS.writeFileSync(sourceFile, "invalid JSON"); const failed = NodeChildProcess.spawnSync(process.execPath, args, { encoding: "utf8" }); assert.strictEqual(failed.status, 1); - assert.include(failed.stderr || failed.stdout, "Failed to decode source"); + assert.include(failed.stderr + failed.stdout, "Failed to decode source"); assert.deepEqual(JSON.parse(NodeFS.readFileSync(stateFile, "utf8")), state); } finally { NodeFS.rmSync(root, { recursive: true, force: true });