From 96de128c7edbe6a1809bea55c486510e609d7590 Mon Sep 17 00:00:00 2001 From: Yordis Prieto Date: Fri, 9 Oct 2026 19:40:43 -0400 Subject: [PATCH] test(server): the ACP process-tree test no longer collides with the runner's own pid Signed-off-by: Yordis Prieto --- .../src/provider/acp/AcpSessionRuntime.processTree.test.ts | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/apps/server/src/provider/acp/AcpSessionRuntime.processTree.test.ts b/apps/server/src/provider/acp/AcpSessionRuntime.processTree.test.ts index 81d499733caf..af7b77fd90e5 100644 --- a/apps/server/src/provider/acp/AcpSessionRuntime.processTree.test.ts +++ b/apps/server/src/provider/acp/AcpSessionRuntime.processTree.test.ts @@ -655,8 +655,11 @@ describe("terminatePosixOwnedProcessTree", () => { it.live("rotates more than 64 live parents without scanning retained tombstones", () => Effect.gen(function* () { + // The server fixture's process group is the runner's real pid, so a synthetic + // parent sharing it would be skipped as the server's own group. + const parentPidBase = process.pid < 500_000 ? 500_000 : 1_000; const parents = Array.from({ length: 130 }, (_, index) => - identity(1_000 + index, 100, 1_000 + index, 1_000 + index), + identity(parentPidBase + index, 100, parentPidBase + index, parentPidBase + index), ); let childListReads = 0; let identityCalls = 0;