Allow ACP Stop integration tests time for process startup

CI exhausted the five-second outer timeout in both interrupted-session fallback cases. These tests start and stop multiple real ACP clients, while cancellation alone has a five-second grace period. The same-session case also finished at 4.9 seconds in that job.

Give these multi-process cases the existing fifteen-second budget used by the interrupted-write test. Keep all cancellation and resume assertions, product grace periods, and the dedicated forced-exit deadline test unchanged.

Validation: CI supplied the red reproduction. The current Stop suite passed all six cases before the timeout-only change. Focused Stop, process-control, and engine checks passed after the change.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Devin FoleyandPaperclip committed 2026-11-12 21:08:48 -08:00
1 parent 1c21edbc9e
commit 2a758c7dde
1 file changed
+2 -2
@@ -46,7 +46,7 @@ it('stops an actual ACP process and resumes its established session with the new
const launches = (await fs.readFile(path.join(root, 'run-env'), 'utf8')).trim().split('\n').map(line => JSON.parse(line));
expect(launches.map(launch => launch.runId)).toEqual(['stop-test', 'follow-up']);
expect(launches[1].tokenHash).toBe(createHash('sha256').update('follow-up-test-token').digest('hex'));
});
}, 15000);
it('continues after an interrupted write without replaying that write', async () => {
const { root, ctx, abort, started, execute } = await setup('write');
const running = execute(ctx);
@@ -89,7 +89,7 @@ it.each(['missing session', 'changed configuration'])('starts a new turn when th
}
expect(next.exitCode, JSON.stringify(next)).toBe(0);
expect((await fs.readFile(path.join(root, 'prompts'), 'utf8')).trim().split('\n')).toHaveLength(2);
});
}, 15000);
it('keeps the Stop deadline active after cancellation returns until provider exit', async () => {
const { ctx, abort, started, execute } = await setup();