Skip to content
This repository was archived by the owner on Oct 20, 2026. It is now read-only.

test: the protocol-71 real-stack cases get 30 s each - #8

Merged
drietsch merged 1 commit into
mainfrom
fix/p71-test-timeout
Oct 17, 2026
Merged

drietsch merged 1 commit into
mainfrom
fix/p71-test-timeout

Conversation

@drietsch

Copy link
Copy Markdown
Contributor

The canary.17 publish failed twice on the same case, protocol71-real-core.spec.ts › "the text variable is exported as InDesign's own …": "Test timed out in 5000ms". The publish job runs the whole suite on a shared 4-core runner (151 s of test time in 69 s of wall time). Alone, the case takes 0.85 s locally.

The file's describe now sets { timeout: 30_000 }, as the other real-core specs already do (objects-panel-real-core: 120 s, duckdb-browser: 60 s). No behaviour change; all 5 cases pass locally with REQUIRE_REAL_CORE=1 REQUIRE_REAL_ENGINE=1. A merge publishes 0.1.0-canary.17.

🤖 Generated with Claude Code

The publish job runs the whole suite on a shared 4-core runner, and the IDML
export case went past vitest's 5 s default twice (it takes under a second
alone), so canary.17 never published. The other real-core specs already set
their own limits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@drietsch
drietsch merged commit 11799a6 into main Oct 17, 2026
4 of 5 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant