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#L49

expect(received).toHaveLength(expected) Expected length: 2 Received length: 1 Received array: [{"rest": "PASS __tests__/bar.spec.js PASS __tests__/foo.spec.js", "summary": "Test Suites: 2 passed, 2 total Tests: 4 passed, 4 total Snapshots: 0 total Time: <<REPLACED>> Ran all test suites."}] at Object.toHaveLength (e2e/__tests__/watchModePatterns.test.ts:49:19)

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

expect(received).toMatchSnapshot() Snapshot name: `can press "p" to filter by file name 1` - Snapshot - 4 + Received + 1 @@ -30,10 +30,7 @@ <moveCursorToColumn1> <eraseScreenDown> pattern › bar <saveCursorPosition> <moveCursorToRow6Column15> - <restoreCursorPosition> - - <moveCursorDownBy1Row> - <eraseScreenDown> + <restoreCursorPosition> " at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:48:18)

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

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 2` - Snapshot - 0 + Received + 1 PASS __tests__/bar.spec.js ✓ bar › 1 snapshot updated. + 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 updated from 1 test suite. at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)

processChild › handles circular inequality properly: 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:56:35)

processChild › handles circular inequality properly: undefined#L1

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

processChild › handles circular inequality properly: undefined#L1

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

processChild › handles circular inequality properly: 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:56:35)

processChild › handles circular inequality properly: undefined#L1

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

processChild › handles circular inequality properly: undefined#L1

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

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

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

Windows with shard 1/4 / Node v22.x

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

Windows with shard 2/4 / Node v20.x

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