chore(deps): lock file maintenance #13625
Triggered via pull request
April 28, 2024 08:07
Status
Failure
Total duration
6h 52m 45s
Artifacts
–
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 16s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 55s
TypeScript Compatibility
5m 50s
Typecheck Examples and Tests
3m 53s
Lint
1m 50s
Validate Yarn dependencies and constraints
14s
Node LTS on Ubuntu with leak detection
1m 10s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
14 errors and 8 warnings
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)
|
gets changed files for hg:
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)
|
gets changed files for hg:
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)
|
monitors only root paths for hg:
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)
|
monitors only root paths for hg:
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)
|
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)
|
default reporter › prints failure messages when total number of test suites is over summaryThreshold:
e2e/__tests__/summaryThreshold.test.ts#L21
expect(received).toMatch(expected)
Expected pattern: /Summary of all failing tests(\n|.)*expect\(1\)\.toBe\(0\)/
Received string: "node:events:497·
throw er; // Unhandled 'error' event·
^···
Error: kill EPERM·
at ChildProcess.kill (node:internal/child_process:512:26)·
at ChildProcessWorker.killChild (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:999:17)·
at ChildProcessWorker.forceExit (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1004:33)·
at Timeout._onTimeout (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:567:16)·
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)·
at ChildProcessWorker.killChild (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:999:17)·
[... 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 Object.toMatch (e2e/__tests__/summaryThreshold.test.ts:21:22)
|
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)
|
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)
|
Runtime CLI › displays script output:
undefined#L1
expect(received).toMatch(expected)
Expected substring: "Hello, world!"
Received string: ""
at Object.toMatch (packages/jest-repl/src/__tests__/runtime_cli.test.js:36:52)
|
macOS with shard 3/3 / Node v22.x
The job running on runner GitHub Actions 8 has exceeded the maximum execution time of 360 minutes.
|
macOS with shard 3/3 / Node v22.x
The operation was canceled.
|
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
|
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
|
Windows with shard 2/4 / Node v21.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
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 2 failed. Reason: Child_process exited with error code 1
|