ci/gha: Add ARM64 QEMU jobs for clang and clang-snapshot #105
Triggered via pull request
August 30, 2023 17:04
Status
Failure
Total duration
1h 30m 22s
Artifacts
–
ci.yml
on: pull_request
Build Docker image
34m 29s
x64 (MSVC): C++ (public headers)
22s
SageMath prover
1m 13s
Matrix: x86_64: macOS Monterey
Matrix: win64-native
s390x (big-endian): Linux (Debian stable, QEMU)
14m 58s
ppc64le: Linux (Debian stable, QEMU)
11m 14s
C++ -fpermissive (entire project)
9m 23s
C++ (public headers)
3m 58s
Matrix: ARM32: Linux (Debian stable, QEMU)
Matrix: ARM64: Linux (Debian stable, QEMU)
Matrix: i686: Linux (Debian stable)
Matrix: x86_64: Linux (Debian stable)
Matrix: mingw_debian
Matrix: MSan
Matrix: UBSan, ASan, LSan
Matrix: Valgrind (memcheck)
Annotations
19 errors and 8 warnings
ARM64: Linux (Debian stable, QEMU) (clang-snapshot --target=aarch64-linux-gnu, -fsanitize=memory ...
Process completed with exit code 2.
|
ARM64: Linux (Debian stable, QEMU) (clang --target=aarch64-linux-gnu, -fsanitize=memory -fsanitiz...
buildx failed with: ERROR: failed to solve: debian:stable-slim: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/debian/manifests/stable-slim: 503 Service Unavailable
|
ARM64: Linux (Debian stable, QEMU) (clang --target=aarch64-linux-gnu, -fsanitize=memory -fsanitiz...
Process completed with exit code 77.
|
x86_64 (mingw32-w64): Windows (Debian stable, Wine)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/debian/blobs/sha256:976677eb458219b3b4687dc52ffa200150bd62975fe6d807e5a049a31def33b6: 503 Service Unavailable
|
UBSan, ASan, LSan (clang, auto)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to authorize: failed to fetch oauth token: unexpected status from POST request to https://auth.docker.io/token: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (2, 2, clang)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/debian/blobs/sha256:976677eb458219b3b4687dc52ffa200150bd62975fe6d807e5a049a31def33b6: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (2, 2, clang)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/debian/blobs/sha256:976677eb458219b3b4687dc52ffa200150bd62975fe6d807e5a049a31def33b6: 503 Service Unavailable
|
MSan (-fsanitize=memory -fsanitize-recover=memory -g)
buildx failed with: ERROR: failed to solve: debian:stable-slim: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/debian/manifests/stable-slim: 503 Service Unavailable
|
i686: Linux (Debian stable) (clang --target=i686-pc-linux-gnu -isystem /usr/i686-linux-gnu/include)
buildx failed with: ERROR: failed to solve: debian:stable-slim: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/debian/manifests/stable-slim: 503 Service Unavailable
|
s390x (big-endian): Linux (Debian stable, QEMU)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/debian/blobs/sha256:f423885d3d1039f2c0dd54c9737e762d933153ee24a153f664e0c19dbc8313e1: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (int128, clang)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to authorize: failed to fetch oauth token: unexpected status from POST request to https://auth.docker.io/token: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (int128, clang-snapshot)
buildx failed with: ERROR: failed to solve: debian:stable-slim: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/debian/manifests/stable-slim: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (-O0, no, gcc)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/debian/blobs/sha256:f423885d3d1039f2c0dd54c9737e762d933153ee24a153f664e0c19dbc8313e1: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (int64, yes, clang)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/debian/blobs/sha256:976677eb458219b3b4687dc52ffa200150bd62975fe6d807e5a049a31def33b6: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (int128, yes, yes, yes, clang-snapshot)
buildx failed with: ERROR: failed to solve: debian:stable-slim: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/debian/manifests/stable-slim: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (int128, yes, yes, yes, gcc)
buildx failed with: ERROR: failed to solve: debian:stable-slim: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/debian/manifests/stable-slim: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (int64, yes, clang-snapshot)
buildx failed with: ERROR: failed to solve: debian:stable-slim: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/debian/blobs/sha256:f423885d3d1039f2c0dd54c9737e762d933153ee24a153f664e0c19dbc8313e1: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (no, yes, yes, yes, -DVERIFY, clang)
buildx failed with: ERROR: failed to solve: debian:stable-slim: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/debian/manifests/stable-slim: 503 Service Unavailable
|
x86_64: Linux (Debian stable) (int128, x86_64, yes, gcc)
buildx failed with: ERROR: failed to solve: failed to copy: read tcp 172.17.0.2:34546->52.239.170.164:443: read: connection timed out
|
Build Docker image
Error: Error: No such object: buildx_buildkit_builder-0b3a9f9c-030b-44bd-952c-3daee058b9620
|
C++ (public headers)
Error: Error: No such object: buildx_buildkit_builder-22020e9f-a05a-4758-9450-69da46b371110
|
ARM64: Linux (Debian stable, QEMU) (clang-snapshot --target=aarch64-linux-gnu, -fsanitize=memory ...
Error: Error: No such object: buildx_buildkit_builder-a568de36-1226-4764-bed9-f860799af74f0
|
x86_64: Linux (Debian stable) (2, 2, clang)
Error: Error: No such object: buildx_buildkit_builder-4781b0fe-5f61-4d24-a5fb-3a3c23f9d64e0
|
MSan (-fsanitize=memory -fsanitize-recover=memory -g)
Error: Error: No such object: buildx_buildkit_builder-c152c56d-c3ec-49a5-94ed-4dd9b46d0b740
|
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, gcc)
Error: Error: No such object: buildx_buildkit_builder-24b69f01-9a6e-4575-aa8c-f1b488b3b7b50
|
x86_64: Linux (Debian stable) (int128, yes, yes, yes, gcc-snapshot)
Error: Error: No such object: buildx_buildkit_builder-1af5b2d1-5c2f-40cd-b6aa-6bfa1833d18f0
|
Valgrind (memcheck) (i686-linux-gnu-gcc, i686-linux-gnu, no, 2, 2)
Error: Error: No such object: buildx_buildkit_builder-61ca8dec-fe80-4c1e-a435-4e336d222f9a0
|