Skip to content

Give the Elekloader update CLI tests room to run on loaded CI - #615

Merged
repeat98 merged 1 commit into
mainfrom
claude/elekloader-test-timeout
Oct 14, 2026
Merged

repeat98 merged 1 commit into
mainfrom
claude/elekloader-test-timeout

Conversation

@repeat98

Copy link
Copy Markdown
Owner

The first case of elekloader update CLI failed module-contract on #577 with Test timed out in 5000ms. It passed locally in 1.3 s. Each case spawns the real update CLI, which has its own 20 s limit per call, but the test itself used vitest's 5 s default, so a loaded CI runner running 4 workers crossed it.

#614 made the CLI do a little more work (it assembles the catalogue from the module records and verifies the served folder), which moved this case over the line. Every module PR that runs the full suite would hit it.

Change

One option on the describe: { timeout: 60_000 }, above two 20 s CLI calls. No behaviour or assertion changes.

Tested

  • src/tooling/elekloader-update.test.ts: 11 of 11 pass; lint clean.
  • Not reproduced locally: on this Mac the slowest case takes 1.3 s. The cause is the CI log (Test timed out in 5000ms) and the runner's measured 18.9 s for the file.

🤖 Generated with Claude Code

Each case runs the real update CLI, up to 20 s per call, but vitest's
default 5 s test timeout failed the first case on a loaded runner
("Test timed out in 5000ms") and so failed module-contract on PR #577.
The catalogue now assembles from module records, which made the CLI a
little slower and moved this case over the limit.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@repeat98
repeat98 merged commit 980152b into main Oct 14, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant