Skip to content

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

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

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

Triggered via pull request November 25, 2024 21:15
Status Failure
Total duration 15m 2s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
1m 0s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
1m 16s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 44s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
2m 15s
TypeScript Compatibility
Typecheck Examples and Tests
2m 21s
Typecheck Examples and Tests
Lint
1m 51s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
44s
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

12 errors and 4 warnings
TypeScript Compatibility
Process completed with exit code 1.
Typecheck Examples and Tests
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)
--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 (5 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)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
processChild › handles `Symbol`: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
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 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 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)
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/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
Windows with shard 4/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1