Repository navigation
test: size the formal route tree timeout for a loaded host - #168
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wec9b4589-27
Summary
The nightly
ci / Stressrun of 2026-11-20 (run 44660723759, 1 of 3 runs) failed indist/test/formal-route-tree.test.jswithTimeout of 2000ms exceededbeside 16 busy loops. The property test runs 200 generated scenarios, about 360 ms on an idle host, and had mocha's default 2000 ms.The test now sets its own timeout:
max(30 s, FORMAL_RUNS * 150 ms). The generated tree is unchanged, so the checked property and the seed's coverage stay the same. The timeout also scales with--full(2000 runs) of the formal-route-tree skill..agents/skills/formal-route-tree/check.mjsis run by no CI leg (only by the skill), so itsspawnSync("pnpm", …)is left alone.Proof
Before (nightly run 44660723759):
Error: Timeout of 2000ms exceededinregisters, matches and unregisters like the reference….After, locally:
✔ registers, matches and unregisters like the reference… (356ms), 1 passing.Local reproduction beside 64 busy loops (4 per CPU on 16 CPUs), same test file:
1 failing,Error: Timeout of 2000ms exceeded✔ registers, matches and unregisters like the reference… (12675ms), 1 passingA manual dispatch of this branch passed its checks (run 44826154957). The nightly tier cannot be dispatched by hand (
ci-tierreturnsnightlyonly forschedule); the next scheduled nightly is the proof.flowchart LR A[mocha runs the test] --> B{timeout} B -->|before: 2000 ms| C[loaded host: killed] B -->|after: max 30 s, runs x 150 ms| D[property completes]Follow-ups