aborted

kill EPERM at ChildProcessWorker.kill [as killChild] (packages/jest-worker/build/index.js:999:17)

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

expect(received).toMatchSnapshot() Snapshot name: `collects coverage only from specified file 1` - Snapshot - 6 + Received + 0 - ----------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - ----------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - file.js | 100 | 100 | 100 | 100 | - ----------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:49:18)

expect(received).toMatchSnapshot(hint) Snapshot name: `can press "t" to filter by test name: test results 2` - Snapshot - 0 + Received + 2 PASS __tests__/bar.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. + PASS __tests__/foo.spec.js at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70:18)

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)

Final attempt failed. Child_process exited with error code 1

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)

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

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