Skip to content

Commit e401099

Browse files
t3dotggclaude
andcommitted
test(server): restart replay tests run startup recovery
The second runtime in the replay recovery tests skipped the startup recovery a real server runs. When the first runtime closed while its checkpoint capture was still leased, that row stayed running and blocked every later effect on the thread, so the next turn never started. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent e57c093 commit e401099

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

‎apps/server/src/orchestration-v2/testkit/OrchestratorReplayRecovery.integration.test.ts‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,8 @@ const runCursorRecovery = Effect.fn("runCursorRecovery")(function* (input: {
243243
runtimePolicyOverride: { cwd: tempDir },
244244
},
245245
harness,
246-
options,
246+
// A real restart requeues effects, like checkpoint capture, the first runtime left running.
247+
{ ...options, recoverOnStartup: true },
247248
),
248249
);
249250

@@ -336,7 +337,7 @@ describe("orchestrator replay recovery", () => {
336337
runtimePolicyOverride: { cwd: workspace },
337338
},
338339
harness,
339-
options,
340+
{ ...options, recoverOnStartup: true },
340341
);
341342

342343
assertBaseProjection({
@@ -436,7 +437,7 @@ describe("orchestrator replay recovery", () => {
436437
runtimePolicyOverride: { cwd: workspace },
437438
},
438439
harness,
439-
options,
440+
{ ...options, recoverOnStartup: true },
440441
),
441442
);
442443
yield* assertComplete;

0 commit comments

Comments
 (0)