Nightly Validation failed: windows-latest / Node 20 #348

Activity

1. coderabbitai commented on Jun 23, 2026

   

   coderabbitaiBot

   on Jun 23, 2026 – with coderabbitai

   More actions

   🔗 Related PRs

   #325 - Fix Windows nightly test portability [merged]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
2. unbraind commented on Jun 23, 2026

   

   unbraind

   on Jun 23, 2026

   Owner

   More actions

   Investigated (tracked in pm-2kkl). This is not a test-assertion failure: 246 of 247 test files pass with 0 failed assertions. The single error is a vitest pool crash —

   Error: [vitest-pool]: Worker forks emitted error.
   Caused by: Error: Worker exited unexpectedly
   

   i.e. a worker process crashed during teardown after its tests had already passed, almost certainly a native resource (LanceDB or the OTLP gRPC exporter) not releasing cleanly on Windows. It is a distinct symptom from the prior Windows nightlies — GH-340/pm-zpe7 (OTLP cleanup EBUSY) and pm-i84i (file:// TS-import SyntaxError).

   Non-blocking for releases: the daily auto-release gate is green (npm 2026.6.23 published), and the per-PR Windows regression (Node 20) job — the deterministic Windows oracle — passes on current main (e.g. PR #349). The nightly failure is intermittent worker teardown, not a reproducible logic break.

   Fixing it confidently needs a Windows runner to reproduce (the crash gives no file attribution, and it does not reproduce on Linux/macOS). Tracked at pm-2kkl for a targeted teardown-hardening pass once a Windows repro is available; leaving this open as the live signal.
3. unbraind

   added a commit that references this issue on Jun 23, 2026

   feat(sdk): add extension version compatibility preflight (#350)

   ...

   d2ab679
4. github-actions commented on Jun 24, 2026

   

   github-actionsBot

   on Jun 24, 2026 – with GitHub Actions

   Author

   More actions

   Scheduled Nightly Validation failed for windows-latest / Node 20.

   Run: https://github.com/unbraind/pm-cli/actions/runs/28083306766
   Commit: 8f9d3cb

   Investigate before trusting the next daily release.
5. unbraind

   added a commit that references this issue on Jun 24, 2026

   fix(sdk): harden TypeScript package runtime loading

   ...

   370e7fc
6. unbraind

   closed this as completedin #353on Jun 24, 2026
7. unbraind

   added 3 commits that reference this issue on Jun 25, 2026

   fix(windows): resolve Node 24 nightly — telemetry detached-spawn, run…

   ...

   6f88efc

   test: share background signal dispatch helper

   ...

   6c27a3a

   Fix Windows background test-run signal coverage (#377)

   ...

   b087af6
8. unbraind commented on Jul 11, 2026

   

   unbraind

   on Jul 11, 2026

   Owner

   More actions

   pm tracker item:

   • pm-2kkl — Nightly Validation failed: windows-latest / Node 20 #348/Nightly Validation failed: windows-latest / Node 24 #376: Windows nightly Vitest worker fork exits unexpectedly after passing tests