From 01ca02ad04854c786f41844604ae1302bee511c0 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 2 Sep 2026 01:05:51 +0200 Subject: [PATCH] A machine works through its queue, and the wait allows for it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit With caught-up finally an equality, the last red test turned out to be telling the truth about something real: declarations queue, the machine applies them one at a time at half a minute each, and by the twenty- fifth test it is minutes behind the latest push. 240 seconds was not a generous bound on one apply — it was an accidental bound on the whole backlog. Doubled rather than tuned, and the real remedy filed instead: a machine asked to be five successive things should become the last one, which is a decision about the link rather than about this timeout (novox/hq 04-ISSUES/031). --- test/integration/mesh.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/integration/mesh.test.ts b/test/integration/mesh.test.ts index 48f5890..5f2923f 100644 --- a/test/integration/mesh.test.ts +++ b/test/integration/mesh.test.ts @@ -120,7 +120,7 @@ async function mesh(command: string, timeoutMs?: number): Promise { * to become right by being waited for, and a refusal read after two minutes of polling is the same * refusal, later. */ -async function settled(node: string, withinMs = 240_000): Promise { +async function settled(node: string, withinMs = 480_000): Promise { const until = Date.now() + withinMs; let last = ""; while (Date.now() < until) {