Skip to content

add fedora sccache worker #82

add fedora sccache worker

add fedora sccache worker #82

Triggered via pull request August 30, 2024 09:33
Status Failure
Total duration 20s
Artifacts

build-dockers.yml

on: pull_request
Matrix: build-and-push-image
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 13 warnings
Build CI container for ubuntu-20.04-3.9
buildx failed with: ERROR: resolve : lstat ci/ci-ubuntu-20.04-3.9: no such file or directory
Build CI container for debian-11-3.10
buildx failed with: ERROR: resolve : lstat ci/ci-debian-11-3.10: no such file or directory
Build CI container for fedora-40-3.10
buildx failed with: ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 32aaff51-f71e-4da3-a768-7eba5267b3ba::er6paz6lsf6vrsthbtxkhbpbc: "/config": not found
Build CI container for debian-10-3.9
buildx failed with: ERROR: resolve : lstat ci/ci-debian-10-3.9: no such file or directory
Build CI container for fedora-38-3.10
buildx failed with: ERROR: resolve : lstat ci/ci-fedora-38-3.10: no such file or directory
Build CI container for ubuntu-18.04-3.9
buildx failed with: ERROR: resolve : lstat ci/ci-ubuntu-18.04-3.9: no such file or directory
Build CI container for debian-i386-11-3.10
buildx failed with: ERROR: resolve : lstat ci/ci-debian-i386-11-3.10: no such file or directory
Build CI container for ubuntu-22.04-3.9
buildx failed with: ERROR: resolve : lstat ci/ci-ubuntu-22.04-3.9: no such file or directory
Build CI container for ubuntu-18.04-3.8
buildx failed with: ERROR: resolve : lstat ci/ci-ubuntu-18.04-3.8: no such file or directory
Build CI container for debian-12-3.10
buildx failed with: ERROR: resolve : lstat ci/ci-debian-12-3.10: no such file or directory
Build CI container for fedora-37-3.9
buildx failed with: ERROR: resolve : lstat ci/ci-fedora-37-3.9: no such file or directory
Build CI container for fedora-39-3.10
buildx failed with: ERROR: resolve : lstat ci/ci-fedora-39-3.10: no such file or directory
Build CI container for ubuntu-24.04-3.10
buildx failed with: ERROR: resolve : lstat ci/ci-ubuntu-24.04-3.10: no such file or directory
Build CI container for ubuntu-20.04-3.9
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for debian-11-3.10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for fedora-40-3.10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for debian-10-3.9
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for fedora-38-3.10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for ubuntu-18.04-3.9
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for debian-i386-11-3.10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for ubuntu-22.04-3.9
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for ubuntu-18.04-3.8
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for debian-12-3.10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for fedora-37-3.9
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for fedora-39-3.10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build CI container for ubuntu-24.04-3.10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/