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 "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)

handles a bad revision for "changedSince": e2e/Utils.ts#L107

EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\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

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

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

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 - 5 + Received + 5 @@ -67,36 +67,36 @@ START "nine" at log (__tests__/concurrent.test.js:15:11) console.log - END: "nine" + END: "five" at log (__tests__/concurrent.test.js:15:11) console.log START "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "five" + END: "nine" 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)

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 - 4 + Received + 4 @@ -67,21 +67,21 @@ START "nine" at log (__tests__/concurrent.test.js:15:11) console.log - END: "nine" + END: "five" at log (__tests__/concurrent.test.js:15:11) console.log START "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "five" + END: "nine" at log (__tests__/concurrent.test.js:15:11) console.log END: "six" @@ -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 - 2 + Received + 2 @@ -67,21 +67,21 @@ START "nine" at log (__tests__/concurrent.test.js:15:11) console.log - END: "nine" + END: "five" at log (__tests__/concurrent.test.js:15:11) console.log START "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "five" + END: "nine" at log (__tests__/concurrent.test.js:15:11) console.log END: "six" 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 - 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

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

EEXIST: file already exists, symlink 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\symlinked-files\test.js' -> 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\test-files\test.js' at symlinkSync (e2e/Utils.ts:158:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:30:16)

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 `BigInt`: 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:85:35)

processChild › handles `BigInt`: undefined#L1

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

processChild › handles `BigInt`: undefined#L1

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

processChild › handles `Symbol`: undefined#L1

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

processChild › handles `Symbol`: 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 functions: 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:98:35)

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

EBUSY: resource busy or locked, rmdir '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)

prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Validate Yarn dependencies and constraints

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Node LTS on Ubuntu with leak detection

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Lint

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 1/4 / Node v22.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 1/4 / Node v23.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 1/4 / Node v20.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 1/4 / Node v18.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Node LTS on Ubuntu with coverage (4/4)

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 1/4 / Node v16.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Node LTS on Ubuntu with coverage (1/4)

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

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

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 2/4 / Node v22.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 2/4 / Node v20.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 2/4 / Node v23.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Node LTS on Ubuntu with coverage (3/4)

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 2/4 / Node v18.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Node LTS on Ubuntu with coverage (2/4)

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 2/4 / Node v16.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 2/4 / Node LTS using jest-jasmine2

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Typecheck Examples and Tests

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 3/4 / Node LTS using jest-jasmine2

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

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

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 3/4 / Node v22.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 4/4 / Node v20.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 3/4 / Node v18.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 3/4 / Node v20.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 3/4 / Node v23.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 4/4 / Node v18.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 4/4 / Node v23.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 3/4 / Node v16.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 4/4 / Node v22.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Ubuntu with shard 4/4 / Node v16.x

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

TypeScript Compatibility

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

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