ci: raise VS Code Storybook heap limit#11014
Merged
Merged
Conversation
marius-kilocode
approved these changes
Jun 8, 2026
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
2 participants
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
Raise the Node heap limit to 4 GB for the VS Code webview visual-regression job.
The workflow consistently reached the end of Vite's 5,799-module transform and then aborted at Node's default ~2 GB heap limit before screenshot comparison. The first CI experiment scoped the override only to
Build Storybook: that step passed, then Playwright's independently started Storybook web server hit the same heap limit. The job-level override covers both Storybook processes while remaining isolated from the separate kilo-ui job.This same failure occurred twice on #10879 and on an unrelated VS Code PR, so it is not caused by a particular visual change.
Validation