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)

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:62:24)

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)

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)

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

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

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

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

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

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