expect(received).toMatchSnapshot(hint) Snapshot name: `can press "u" to update snapshots: test results 1` - Snapshot - 0 + Received + 1 @@ -14,7 +14,8 @@ | ^ at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35) › 1 snapshot failed. + 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. Snapshot Summary › 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them." at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)

Could not find test summary in the output. OUTPUT: PASS __tests__/a.test.js ✓ a (5 ms) 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 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 processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v21.6.2 at extractSummary (e2e/Utils.ts:243:11) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:244:43)

expect(received).toMatch(expected) Expected pattern: /PASS/ Received string: "FAIL __tests__/test.js·· ● Test suite failed to run· kill EPERM· at ChildProcessWorker.killChild (../../../packages/jest-worker/build/index.js:999:17)· Test Suites: 1 failed, 1 total Tests: 2 passed, 2 total Snapshots: 0 total Time: 0.639 s Ran all test suites." at Object.toMatch (e2e/__tests__/transform.test.ts:299:20)

EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)

EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)

EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)

expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at toBe (e2e/__tests__/multiProjectRunner.test.ts:204:22)

Final attempt failed. Child_process exited with error code 1

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)

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 2 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 2 failed. Reason: Child_process exited with error code 1