fix(docs): raise sdk-reference suite timeouts for slower CI runners - #2747
Open
miguelg719 wants to merge 1 commit into
Open
fix(docs): raise sdk-reference suite timeouts for slower CI runners#2747miguelg719 wants to merge 1 commit into
miguelg719 wants to merge 1 commit into
Conversation
The suites scan every v4 MDX file; #2698 grew the scan set enough that CI runners exceed vitest's 5s default per test (locally ~3.9s). Set a 30s suite timeout on both describes. Blocks every PR's TypeScript unit job until fixed.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
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.
TypeScript unit is failing on every PR since #2698 merged:
packages/docs/tests/sdk-reference.test.tsscans all v4 MDX files, #2698 grew the scan set, and CI runners now exceed the 5s vitest default (locally ~3.9s on M-series — right at the edge). Two consecutive CI runs failed identically on #2743.One-line-per-suite fix: 30s suite timeout on both describes. Verified: 27/27 pass locally in 4.15s.
Summary by cubic
Raises
vitestsuite timeouts in the docs SDK reference tests to 30s to stabilize CI on slower runners. Previously both suites used the 5s default and timed out after #2698 expanded the MDX scan set.{ timeout: 30_000 }to the "SDK reference surface" and "Mintlify customization boundary"describeblocks.vitest.Written for commit d85f6ce. Summary will update on new commits.