chore(pre-commit): update crate-ci/typos to v1.30.2 #776
Triggered via pull request
September 16, 2024 21:07
renovate[bot]
Status
Failure
Total duration
45m 6s
Artifacts
–
Annotations
8 errors and 4 warnings
|
test (ubuntu-latest, 3.8)
The hosted runner: GitHub Actions 7 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (3.5, ubuntu-20.04, 'virtualenv<20.22.0')
The hosted runner: GitHub Actions 13 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (ubuntu-latest, 3.11)
The hosted runner: GitHub Actions 16 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (ubuntu-latest, 3.9)
The hosted runner: GitHub Actions 15 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (ubuntu-latest, pypy-3.9)
The hosted runner: GitHub Actions 19 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (ubuntu-latest, 3.10)
The hosted runner: GitHub Actions 1 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (3.6, ubuntu-20.04, 'virtualenv<20.22.0')
The hosted runner: GitHub Actions 18 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (ubuntu-latest, pypy-3.10)
The hosted runner: GitHub Actions 17 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (ubuntu-latest, 3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
test (ubuntu-latest, 3.13.0-alpha - 3.13)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
test (ubuntu-latest, 3.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|