expect(received).toMatchSnapshot() Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1` - Snapshot - 11 + Received + 0 - Error: Jest: Failed to parse the TypeScript config file <<REPLACED>> - SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)' - ,---- - 1 | export default i'll break this file yo - : ^^^^^^^^^^^^^^^^^^^^^^ - `---- - x Unterminated string constant - ,---- - 1 | export default i'll break this file yo - : ^^^^^^^^^^^^^^^^^^^^^^ - `---- at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)

on node >=23.6 › invalid JS in jest.config.ts (node with native TS support): e2e/__tests__/jest.config.ts.test.ts#L158

Ubuntu with shard 1/4 / Node v23.x

Final attempt failed. Child_process exited with error code 1

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)

on node >=23.6 › invalid JS in jest.config.ts (node with native TS support): e2e/__tests__/jest.config.ts.test.ts#L158

macOS with shard 1/3 / Node v23.x

Final attempt failed. Child_process exited with error code 1

on node >=23.6 › invalid JS in jest.config.ts (node with native TS support): e2e/__tests__/jest.config.ts.test.ts#L158

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 1` - Snapshot - 0 + Received + 1 PASS __tests__/bar.spec.js PASS __tests__/foo.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. at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)

Windows with shard 1/4 / Node v23.x

Final attempt failed. Child_process exited with error code 1

all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28

expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -92,16 +92,16 @@ END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent.test.js:15:11) console.log - END: "eight" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)

all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28

expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 3 + Received + 3 @@ -82,21 +82,21 @@ END: "five" at log (__tests__/concurrent.test.js:15:11) console.log - END: "six" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log END: "eight" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)

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)

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/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 `Map`: 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)

Node crawler does not pick up symlinked files by default: e2e/Utils.ts#L107

EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)

Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L107