Skip to content

Containers

Containers #1180

Triggered via schedule February 17, 2025 05:17
Status Failure
Total duration 53m 13s
Artifacts

containers.yml

on: schedule
Matrix: deploy-images
upload-gcc-buildcache
0s
upload-gcc-buildcache
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 10 warnings
Build e4s-amazonlinux-2
buildx failed with: ERROR: failed to solve: process "/bin/sh -c git clone https://github.com/spack/spack /spack && export SPACK_ROOT=/spack && . /spack/share/spack/setup-env.sh && spack -e . concretize && spack -e . install && spack -e . gc -y && spack clean -a && rm -rf /spack /spack.yaml /spack.lock /.spack-env /root/.spack" did not complete successfully: exit code: 1
Build pcluster-amazonlinux-2
buildx failed with: ERROR: failed to solve: process "/bin/sh -c yum update -y && amazon-linux-extras install -y epel && yum update -y && yum install -y autoconf automake bzip2 cpio curl environment-modules file findutils gcc gcc-c++ gcc-gfortran gettext git iputils jansson-devel jq libevent-devel libffi-devel libibverbs-core libtool glibc-locale-source m4 make mercurial mlocate ncurses-devel openssl-devel patch patchelf pciutils perl-devel python3-devel python3-pip rsync tar unzip wget which xz zlib-devel && localedef -i en_US -f UTF-8 en_US.UTF-8 && yum clean all && rm -rf /var/cache/yum/*" did not complete successfully: exit code: 13
Build ubuntu-22.04
buildx failed with: ERROR: failed to solve: process "/bin/sh -c python -m pip install --upgrade pip setuptools wheel && python -m pip install gnureadline boto3 pyyaml pytz minio requests clingo && rm -rf ~/.cache" did not complete successfully: exit code: 1
Build ubuntu-24.04
buildx failed with: ERROR: failed to solve: process "/bin/sh -c python3 -m pip install --upgrade pip setuptools wheel && python3 -m pip install gnureadline boto3 pyyaml pytz minio requests clingo && rm -rf ~/.cache" did not complete successfully: exit code: 1
Build e4s-amazonlinux-2
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build e4s-centos-7
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build e4s-fedora-36
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build e4s-ubuntu-18.04
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build e4s-ubuntu-20.04
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build linux-ubuntu22.04-x86_64_v2
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build tutorial-ubuntu-22.04
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build pcluster-amazonlinux-2
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build ubuntu-22.04
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Build ubuntu-24.04
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists