Skip to content

Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS

test: give the pipeline provider-dispatch wait a load-proof timeout (#10916)

Adam Eivy2e771a0c82a7
diff --git a/server/routes/hostControlPipelineProviderDispatch.test.js b/server/routes/hostControlPipelineProviderDispatch.test.js
index 6de9a1a514..5af708b8b7 100644
--- a/server/routes/hostControlPipelineProviderDispatch.test.js
+++ b/server/routes/hostControlPipelineProviderDispatch.test.js
@@ -131,7 +131,12 @@ describe('Pipeline generation never reaches a CLI provider for unauthorized call
sink.runPromptThroughProvider.mockClear();
const response = await post(appFor(address), operation, headers);
expect(response.status, `${operation[0]}: ${JSON.stringify(response.body)}`).toBe(200);
- await vi.waitFor(() => expect(sink.runPromptThroughProvider, operation[0]).toHaveBeenCalledTimes(1));
+ // The run starts asynchronously after the 200; vi.waitFor's 1 s default is
+ // too tight under a loaded pregate, and a generous cap costs nothing on a pass.
+ await vi.waitFor(
+ () => expect(sink.runPromptThroughProvider, operation[0]).toHaveBeenCalledTimes(1),
+ { timeout: 10_000 },
+ );
expect(sink.runPromptThroughProvider.mock.calls[0][0].provider).toEqual(cliProvider);
}
}