Skip to content

Commit cf5f91e

Browse files
committed
test(composed): put the CLI output in the restore-back assertion message
A-reduced fails on Windows with exitCode 1 and the assertion said only "expected 0, got 1". runCli already captures stdout and stderr; the message now carries them, so the next Windows round names the CLI failure instead of leaving it to be guessed at. Diagnostic only.
1 parent fe8fc6f commit cf5f91e

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

‎tests/codex-composed-acceptance.test.ts‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -388,7 +388,9 @@ describe("WP13 composed toggle acceptance", () => {
388388
// The fixture records itself as the active service install, so the
389389
// production ownership preflight admits this home and P08 completes the
390390
// enable transition through the real CLI.
391-
expect(back.exitCode).toBe(0);
391+
// The CLI's own output is the assertion message: a bare "expected 0, got 1" sent two
392+
// Windows CI rounds chasing a timeout that was never the cause.
393+
expect(`exit=${back.exitCode}\nstderr: ${back.stderr}\nstdout: ${back.stdout}`).toContain("exit=0");
392394
expect((await fx.request(server.runtime, "/api/native-integrations/codex", {
393395
method: "PUT", body: JSON.stringify({ enabled: false }),
394396
})).body).toMatchObject({ desiredEnabled: false });

0 commit comments

Comments
 (0)