Skip to content

chore(deps): update dependency @types/node to v22 #14257

chore(deps): update dependency @types/node to v22

chore(deps): update dependency @types/node to v22 #14257

Triggered via pull request December 11, 2024 10:47
Status Failure
Total duration 19m 30s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
57s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
1m 2s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 33s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
2m 11s
TypeScript Compatibility
Typecheck Examples and Tests
2m 11s
Typecheck Examples and Tests
Lint
1m 59s
Lint
Validate Yarn dependencies and constraints
19s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
50s
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

36 errors and 52 warnings
TypeScript Compatibility
Process completed with exit code 1.
Typecheck Examples and Tests
Process completed with exit code 1.
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:6381) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:7307) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:11468) 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)
Node LTS on Ubuntu with coverage (3/4)
Final attempt failed. Child_process exited with error code 1
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:6360) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:7265) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:11374) 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)
Ubuntu with shard 3/4 / Node v23.x
Final attempt failed. Child_process exited with error code 1
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:6381) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:7274) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:11382) 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)
Ubuntu with shard 3/4 / Node v22.x
Final attempt failed. Child_process exited with error code 1
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)
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 2` - Snapshot - 0 + Received + 1 PASS __tests__/bar.spec.js ✓ bar › 1 snapshot updated. + 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 updated from 1 test suite. at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
collects coverage only from multiple specified files: e2e/__tests__/coverageReport.test.ts#L66
expect(received).toMatchSnapshot() Snapshot name: `collects coverage only from multiple specified files 1` - Snapshot - 7 + Received + 0 - --------------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - --------------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - file.js | 100 | 100 | 100 | 100 | - otherFile.js | 100 | 100 | 100 | 100 | - --------------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:66:18)
Windows with shard 1/4 / Node LTS using jest-jasmine2
Final attempt failed. Child_process exited with error 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)
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)
processChild › handles `Symbol`: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles `Symbol`: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
--findRelatedTests flag › coverage configuration is applied correctly: node:internal/child_process#L511
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:244:43)
outputs coverage report when text and text-summary is requested: e2e/__tests__/coverageReport.test.ts#L144
expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at Object.toBe (e2e/__tests__/coverageReport.test.ts:144:20)
collects coverage only from multiple specified files: e2e/__tests__/coverageReport.test.ts#L66
expect(received).toMatchSnapshot() Snapshot name: `collects coverage only from multiple specified files 1` - Snapshot - 7 + Received + 0 - --------------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - --------------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - file.js | 100 | 100 | 100 | 100 | - otherFile.js | 100 | 100 | 100 | 100 | - --------------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:66:18)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:13641) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:15019) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:25830) 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)
macOS with shard 2/3 / Node v23.x
Final attempt failed. Child_process exited with error code 1
--findRelatedTests flag › coverage configuration is applied correctly: e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:3000) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:6456) 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)
Repl › cli › runs without errors: undefined#L1
expect(received).toBe(expected) // Object.is equality Expected: "" Received: "(node:5904) 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)
Windows with shard 3/4 / Node v23.x
Final attempt failed. Child_process exited with error code 1
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Validate Yarn dependencies and constraints
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with leak detection
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
TypeScript Compatibility
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Typecheck Examples and Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (1/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 1/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (4/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (2/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 2/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 4/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (3/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Node LTS on Ubuntu with coverage (3/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
Node LTS on Ubuntu with coverage (3/4)
Attempt 2 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 3/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 3/4 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 3/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Ubuntu with shard 3/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 3/4 / Node v22.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 2 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 4/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / 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 1/4 / Node v22.x
Attempt 2 failed. Reason: Child_process exited with error code 1
macOS with shard 2/3 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
macOS with shard 2/3 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1