Repository navigation
test: size mocha timeouts for a loaded host and the Windows runner - #223
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.
Summary
Wec9b4589-20: the nightly (
ci.yml, schedule) fails two ways, both mocha's default 2000 ms.ci / Stressfailed 3 of 3 since 2026-11-17. Stress runs the suite under load, and the integration suites that talk to the in-memory MongoDB and the booted DMS exceed 2 s (run 44660718110 timed out in 10 tests, spread over[property] external access write-back,data journeys,diagram layout routes,config journeys,editing journeys,a table mapped from an external connectionandexternal connections: changing access). The set that fails changes from run to run, so each of these suites now has a 30 s budget (LOADED_HOST_TIMEOUT_MS).ci / Node .nvmrc on Windows, new on 2026-11-20: the rootbefore allhookseed(redesign.test.ts) timed out at 2 s on the slower Windows runner. It and the siblingseedofschemas-page.test.tsnow have 120 s (SEED_HOOK_TIMEOUT_MS).The two constants live in
src/test/helpers/timeouts.ts. Nothing outsidesrc/testchanges.Related issue
ANT-3515
Verification
Config/CI change, command output before and after:
Before (run 44660718110):
After: a manual run cannot reach the nightly tier (the shared
ci-tieraction returnsnightlyonly forschedule), so the next 02:17 UTC scheduled nightly is the proof.Local reproduction under load:
diagram-routes.test.jsrun throughajs module testbeside one busy loop per CPU: 8 passing (3s).pnpm run typecheck,oxlintandoxfmt --checkonsrc/test: clean.Follow-ups
Checklist