Skip to content

Prevent Windows unit-test heap exhaustion - #887

Closed
rvwatch wants to merge 2 commits into
mainfrom
copilot/fix-windows-unit-tests-failure
Closed

rvwatch wants to merge 2 commits into
mainfrom
copilot/fix-windows-unit-tests-failure

Conversation

@rvwatch

@rvwatch rvwatch commented Nov 14, 2026 •

Copy link
Copy Markdown

Windows test:only jobs repeatedly exhausted Node.js heap after tests had run. The Mocha configuration registered both CommonJS and ESM TypeScript hooks.

  • Change: Remove the redundant ts-node/register hook and keep the ESM loader used by the TypeScript tests:
    "node-option": ["loader=ts-node/esm"]

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
@rvwatch rvwatch changed the title [WIP] Fix failing GitHub Actions job for Windows unit tests Prevent Windows unit-test heap exhaustion Nov 14, 2026
@github-actions

Copy link
Copy Markdown

This PR lacks any commits of the 'fix' or 'feat' type, and therefore will not trigger a release. To silence all further warnings, react to this warning comment (or any other) with the 👀 emoji.

NOTE: If your repo uses squash commits, make sure to add the appropriate conventional commit prefix (e.g., 'fix:', 'feat:', 'chore:', etc) in the squash commit message.

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.

2 participants