Skip to content

docs: add blog post for jest 30 (#15556) #14793

docs: add blog post for jest 30 (#15556)

docs: add blog post for jest 30 (#15556) #14793

Triggered via pull request June 5, 2025 01:58
Status Failure
Total duration 14m 22s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
13s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
19s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
57s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 54s
TypeScript Compatibility
Typecheck Examples and Tests
4m 1s
Typecheck Examples and Tests
Lint
1m 48s
Lint
Validate Yarn dependencies and constraints
14s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
49s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 6 warnings
Lint
Process completed with exit code 1.
notify › does not report --notify flag: e2e/__tests__/detectOpenHandles.ts#L111
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)
processChild › handles `Symbol`: undefined#L0
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles `Symbol`: undefined#L0
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles `Symbol`: 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)
Should throw if watchman used with haste.enableSymlinks: 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)
Should throw if watchman used with haste.enableSymlinks: 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:15:10)
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)
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)
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 `Symbol`: undefined#L0
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles `Map`: 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: 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 circular inequality properly: undefined#L0
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
macOS with shard 2/3 / Node v24.x
Attempt 1 failed. Reason: Child_process exited with error code 1
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 4/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 4/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1