Skip to content

conditionally delete imgs #10

conditionally delete imgs

conditionally delete imgs #10

Triggered via push August 2, 2023 12:17
Status Failure
Total duration 8m 35s
Artifacts

pr.yml

on: push
build-images  /  compute-matrix
7s
build-images / compute-matrix
Matrix: build-images / docker
Matrix: build-images / build-multiarch-manifest
Matrix: build-images / delete-temp-images
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 12 warnings
build-images / docker (11.2.2, 3.10, rockylinux8, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.10)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-rockylinux8-py3.10: no match for platform in manifest sha256:590e5c377831fdb6c70ded2d95b3fd774dcc7b46155185886a057f84ebef0844: not found
build-images / docker (11.2.2, 3.10, rockylinux8, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.10)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-rockylinux8-py3.10: no match for platform in manifest sha256:590e5c377831fdb6c70ded2d95b3fd774dcc7b46155185886a057f84ebef0844: not found
build-images / docker (11.2.2, 3.10, rockylinux8, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.10)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-rockylinux8-py3.10: no match for platform in manifest sha256:590e5c377831fdb6c70ded2d95b3fd774dcc7b46155185886a057f84ebef0844: not found
build-images / docker (11.2.2, 3.10, ubuntu20.04, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.10)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-ubuntu20.04-py3.10: no match for platform in manifest sha256:387bb6afd6891215a0baf84549098a1ae55faaef4237c250b0ae21969b5d43ec: not found
build-images / docker (11.2.2, 3.10, ubuntu20.04, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.10)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-ubuntu20.04-py3.10: no match for platform in manifest sha256:387bb6afd6891215a0baf84549098a1ae55faaef4237c250b0ae21969b5d43ec: not found
build-images / docker (11.2.2, 3.10, ubuntu20.04, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.10)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-ubuntu20.04-py3.10: no match for platform in manifest sha256:387bb6afd6891215a0baf84549098a1ae55faaef4237c250b0ae21969b5d43ec: not found
build-images / docker (11.2.2, 3.9, rockylinux8, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.9)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-rockylinux8-py3.9: no match for platform in manifest sha256:06ce018a98ccdc5f2e8b2e7181491fe63322d8bef9cd9a0f8220b30dd0221b1b: not found
build-images / docker (11.2.2, 3.9, rockylinux8, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.9)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-rockylinux8-py3.9: no match for platform in manifest sha256:06ce018a98ccdc5f2e8b2e7181491fe63322d8bef9cd9a0f8220b30dd0221b1b: not found
build-images / docker (11.2.2, 3.9, ubuntu20.04, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.9)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-ubuntu20.04-py3.9: no match for platform in manifest sha256:9a95f6697f2fdb5cd873edfeb1b27c7258f93e4170b258a26efb9723faa10acc: not found
build-images / docker (11.2.2, 3.9, ubuntu20.04, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.9)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-ubuntu20.04-py3.9: no match for platform in manifest sha256:9a95f6697f2fdb5cd873edfeb1b27c7258f93e4170b258a26efb9723faa10acc: not found
build-images / docker (11.2.2, 3.9, ubuntu20.04, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.9)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-ubuntu20.04-py3.9: no match for platform in manifest sha256:9a95f6697f2fdb5cd873edfeb1b27c7258f93e4170b258a26efb9723faa10acc: not found
build-images / docker (11.2.2, 3.9, rockylinux8, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.9)
buildx failed with: ERROR: failed to solve: rapidsai/mambaforge-cuda:cuda11.2.2-base-rockylinux8-py3.9: no match for platform in manifest sha256:06ce018a98ccdc5f2e8b2e7181491fe63322d8bef9cd9a0f8220b30dd0221b1b: not found
build-images / docker (11.2.2, 3.10, rockylinux8, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.10)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.10, rockylinux8, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.10)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.10, rockylinux8, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.10)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.10, ubuntu20.04, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.10)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.10, ubuntu20.04, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.10)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.10, ubuntu20.04, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.10)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.9, rockylinux8, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.9)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.9, rockylinux8, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.9)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.9, ubuntu20.04, 11.8.0, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.9)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.9, ubuntu20.04, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.9)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.9, ubuntu20.04, 3.10, amd64, arm64) / docker-build (arm64, 11.2.2, ubuntu20.04, 3.9)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1
build-images / docker (11.2.2, 3.9, rockylinux8, ubuntu22.04, amd64, arm64) / docker-build (arm64, 11.2.2, rockylinux8, 3.9)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.306.0. Please update to the latest version 2.307.1