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)

force exits a worker that fails to exit gracefully: e2e/__tests__/workerForceExit.test.ts#L65

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

Option showSeed › --showSeed changes report to output seed: __tests__/get-seed.test.js#L9

Could not find test summary in the output. OUTPUT: PASS __tests__/any-seed.test.js FAIL __tests__/get-seed.test.js ● getSeed expect(received).toBe(expected) // Object.is equality Expected: 1234 Received: 366378594 7 | 8 | test('getSeed', () => { > 9 | expect(jest.getSeed()).toBe(1234); | ^ 10 | }); 11 | at Object.toBe (__tests__/get-seed.test.js:9:26) node:events:498 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 v23.0.0-nightly2024050471a1fa3043 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)

testMatch should able to match file with cjs and mjs extension: e2e/__tests__/testMatch.test.ts#L13

expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at Object.toBe (e2e/__tests__/testMatch.test.ts:13:27)

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)

Option showSeed › --showSeed changes report to output seed: node:internal/child_process#L512

Could not find test summary in the output. OUTPUT: node:events:498 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 v23.0.0-nightly2024050471a1fa3043 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)

Option randomize › --randomize changes report to output seed: __tests__/get-seed.test.js#L9

Could not find test summary in the output. OUTPUT: PASS __tests__/any-seed.test.js FAIL __tests__/get-seed.test.js ● getSeed expect(received).toBe(expected) // Object.is equality Expected: 1234 Received: -158430184 7 | 8 | test('getSeed', () => { > 9 | expect(jest.getSeed()).toBe(1234); | ^ 10 | }); 11 | at Object.toBe (__tests__/get-seed.test.js:9:26) node:events:498 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 v23.0.0-nightly2024050471a1fa3043 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/showSeed.test.ts:21:37)

should not transpile the transformer: e2e/__tests__/globalSetup.test.ts#L168

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

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

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

test-windows / Node nightly on windows-latest (1/4)

Final attempt failed. Child_process exited with error code 1

test-macos / Node Nightly on macos-latest using jest-jasmine2 (3/4)

The job running on runner GitHub Actions 5 has exceeded the maximum execution time of 360 minutes.

test-macos / Node Nightly on macos-latest using jest-jasmine2 (3/4)

The operation was canceled.

test-macos / Node Nightly on macos-latest using jest-jasmine2 (4/4)

The job running on runner GitHub Actions 8 has exceeded the maximum execution time of 360 minutes.