chore(deps): update dependency @types/node to v22 #14212
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
58s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
1m 14s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 22s
TypeScript Compatibility
2m 32s
Typecheck Examples and Tests
2m 15s
Lint
1m 50s
Validate Yarn dependencies and constraints
15s
Node LTS on Ubuntu with leak detection
1m 11s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
8 errors and 7 warnings
Typecheck Examples and Tests:
packages/jest-worker/src/index.ts#L9
Unused '@ts-expect-error' directive.
|
Typecheck Examples and Tests
Process completed with exit code 1.
|
TypeScript Compatibility:
packages/jest-worker/src/index.ts#L9
Unused '@ts-expect-error' directive.
|
TypeScript Compatibility
Process completed with exit code 1.
|
can press "p" to filter by file name:
e2e/__tests__/watchModePatterns.test.ts#L51
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)
|
all 3 test files should complete:
e2e/__tests__/workerRestarting.test.ts#L13
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/workerRestarting.test.ts:13: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)
|
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)
|
Node LTS on Ubuntu with coverage (4/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (1/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (2/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (3/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v16.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
|