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).toBe(expected) // Object.is equality Expected: "" Received: "(node:6357) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:7252) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:11360) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

Final attempt failed. Child_process exited with error code 1

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

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)

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 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:70:18)

expect(received).toMatchSnapshot(hint) Snapshot name: `can press "p" to filter by file name: test results 2` - Snapshot - 0 + Received + 2 PASS __tests__/bar.spec.js ✓ bar 1 ✓ bar 2 + + 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)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:14162) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:15555) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:26614) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

Final attempt failed. Child_process exited with error code 1

expect(received).toMatchSnapshot() Snapshot name: `console printing 1` - Snapshot - 1 + Received + 5 @@ -8,6 +8,10 @@ 11 | new Promise(resolve => setTimeout(resolve, 500)).then(function log() { > 12 | console.log('hello!'); | ^ 13 | }); 14 | }); - 15 |" + 15 | + + at console.log (../../packages/jest-console/build/index.js:147:10) + at log (__tests__/console.test.js:12:13) + " at Object.toMatchSnapshot (e2e/__tests__/consoleAfterTeardown.test.ts:19:24)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:7092) ExperimentalWarning: CommonJS module D:\\a\\jest\\jest\\packages\\jest-util\\build\\index.js is loading ES Module D:\\a\\jest\\jest\\jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:5288) ExperimentalWarning: CommonJS module D:\\a\\jest\\jest\\packages\\jest-util\\build\\index.js is loading ES Module D:\\a\\jest\\jest\\jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:6336) ExperimentalWarning: CommonJS module D:\\a\\jest\\jest\\packages\\jest-util\\build\\index.js is loading ES Module D:\\a\\jest\\jest\\jest.config.mjs using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created)" at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)

Final attempt failed. Child_process exited with error code 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Attempt 2 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 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

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

Attempt 2 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