Skip to content

fix: Fix sources for the new V compiler #35

fix: Fix sources for the new V compiler

fix: Fix sources for the new V compiler #35

Re-run triggered November 16, 2024 05:44
Status Failure
Total duration 17m 45s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 7 warnings
release
Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: jsonlint-macos-x64.zip-763994cfbe4b52fdf80c78b5e606ffdc83fd6600
release
Error: DELETE https://api.github.com/repos/prantlf/v-jsonlint/actions/caches?key=jsonlint-macos-x64.zip-763994cfbe4b52fdf80c78b5e606ffdc83fd6600 failed: 404 Not Found
linux
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
macos
Cache save failed.
macos
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
windows
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
release
Error: DELETE https://api.github.com/repos/prantlf/v-jsonlint/actions/caches?key=jsonlint-macos-x64.zip-763994cfbe4b52fdf80c78b5e606ffdc83fd6600 failed: 404 Not Found
release
Error: DELETE https://api.github.com/repos/prantlf/v-jsonlint/actions/caches?key=jsonlint-macos-x64.zip-763994cfbe4b52fdf80c78b5e606ffdc83fd6600 failed: 404 Not Found
release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/