Could not find test summary in the output. OUTPUT: node:events:497 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:512:26) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:512:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v21.7.3 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)

handles a bad revision for "changedSince": e2e/Utils.ts#L107

EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)

handles a bad revision for "changedSince": e2e/Utils.ts#L107

gets changed files for hg: e2e/Utils.ts#L107

monitors only root paths for hg: e2e/Utils.ts#L107

handles a bad revision for "changedSince": e2e/Utils.ts#L107

EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)

handles a bad revision for "changedSince": e2e/Utils.ts#L107

gets changed files for hg: e2e/Utils.ts#L107

monitors only root paths for hg: e2e/Utils.ts#L107

handles a bad revision for "changedSince": e2e/Utils.ts#L107

notify › does not report --notify flag: e2e/__tests__/detectOpenHandles.ts#L111

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "Jest did not exit one second after the test run has completed.· 'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue." at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L51

expect(received).toMatchSnapshot(hint) Snapshot name: `can press "p" to filter by file name: test results 2` - Snapshot - 0 + Received + 2 PASS __tests__/bar.spec.js ✓ bar 1 ✓ bar 2 + + A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them. at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L51

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L70

expect(received).toMatchSnapshot(hint) Snapshot name: `can press "t" to filter by test name: test results 1` - Snapshot - 0 + Received + 2 PASS __tests__/bar.spec.js + A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them. + PASS __tests__/foo.spec.js at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70:18)

Windows with shard 1/4 / Node v22.x