Skip to content

chore(deps): update yarn to v3.8.2 #13643

chore(deps): update yarn to v3.8.2

chore(deps): update yarn to v3.8.2 #13643

Triggered via pull request May 2, 2024 18:44
Status Success
Total duration 15m 22s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
18s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
21s
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
6m 3s
TypeScript Compatibility
Typecheck Examples and Tests
3m 48s
Typecheck Examples and Tests
Lint
1m 48s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 7s
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

2 errors and 6 warnings
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)
moduleNameMapper with mocking: node:internal/child_process#L512
Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: node:events:497 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:512:26) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:512:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v21.7.3 at json (e2e/runJest.ts:156:11) at Object.<anonymous> (e2e/__tests__/moduleNameMapper.test.ts:52:29)
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 (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
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
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 v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1