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)

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).toBe(expected) // Object.is equality Expected: 26 Received: 0 at Object.toBe (e2e/__tests__/fatalWorkerError.test.ts:42:31)

Could not find test summary in the output. OUTPUT: PASS __tests__/a.test.js ✓ a (4 ms) node:events:498 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:512:26) at listOnTimeout (node:internal/timers:601:17) at processTimers (node:internal/timers:539:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:512:12) [... lines matching original stack trace ...] at processTimers (node:internal/timers:539:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v23.0.0-nightly20240712fc233627ed at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:211:38)

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