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)

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

processChild › handles functions: undefined#L1

Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)

processChild › handles functions: e2e/Utils.ts#L107

EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)

processChild › handles mixed structure: e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36

Process exited at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9) at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:111:35)

can press "u" to update snapshots: e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50

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)

can press "u" to update snapshots: e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50

should call globalSetup function of multiple projects: node:internal/child_process#L511

Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: PASS project-2 project-2/setup2.test.js PASS project-1 project-1/setup1.test.js node:events:497 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:511:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.9.0 at json (e2e/runJest.ts:157:11) at Object.<anonymous> (e2e/__tests__/globalSetup.test.ts:98:29)

outputs coverage report when text-summary is requested: e2e/__tests__/coverageReport.test.ts#L128

expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at Object.toBe (e2e/__tests__/coverageReport.test.ts:128:20)

macOS with shard 2/3 / Node LTS using jest-jasmine2

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

Windows with shard 2/4 / Node v18.x

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

Windows with shard 4/4 / Node LTS using jest-jasmine2

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

Windows with shard 1/4 / Node LTS using jest-jasmine2

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

Windows with shard 1/4 / Node LTS using jest-jasmine2

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