From b9c806da3d38f9d47a194e410c4a44a7fa78a72d Mon Sep 17 00:00:00 2001 From: garrytan Date: Fri, 2 Oct 2026 22:09:13 +0000 Subject: [PATCH] test(pty): the non-blocking judge case is POSIX-only (its fake judge is a shebang script, like the PTY harness it covers) --- test/pty-screen-supervision.test.ts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test/pty-screen-supervision.test.ts b/test/pty-screen-supervision.test.ts index eecab882b..b7ab05fbc 100644 --- a/test/pty-screen-supervision.test.ts +++ b/test/pty-screen-supervision.test.ts @@ -219,7 +219,9 @@ console.log(JSON.stringify({attempts,total:clock,fileWall:1800000})); } finally { fs.rmSync(a.dir, { recursive: true, force: true }); } }, 25_000); -test('the PTY state judge leaves the event loop to concurrent sessions while it waits', () => { +// The fake judge binary is a #! shell script, which Windows cannot exec; the PTY judge itself only +// runs inside the POSIX PTY eval harness, so this case is POSIX-only like the harness it covers. +test.skipIf(process.platform === 'win32')('the PTY state judge leaves the event loop to concurrent sessions while it waits', () => { const dir = fs.mkdtempSync(path.join(os.tmpdir(), 'pty-judge-')); const claude = path.join(dir, 'claude'); const worker = path.join(dir, 'worker.ts');