Skip to content

Remove zypper

Remove zypper #63

Triggered via push August 6, 2025 21:15
Status Failure
Total duration 15m 34s
Artifacts 2

release.yml

on: push
Matrix: e2e
build-base-image-amd64
0s
build-base-image-amd64
build-base-image-arm64
0s
build-base-image-arm64
build-binary-amd64
0s
build-binary-amd64
build-binary-arm64
0s
build-binary-arm64
merge-publish-base-image
0s
merge-publish-base-image
release-controller-image
0s
release-controller-image
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
e2e (Annotations_B)
Process completed with exit code 2.
e2e (Annotations_B)
The strategy configuration was canceled because "e2e.Ingress_Lua_Memory_Leak_m" failed
e2e (Annotations_A|Settings)
The operation was canceled.
e2e (Annotations_A|Settings)
The strategy configuration was canceled because "e2e.Ingress_Lua_Memory_Leak_m" failed
e2e (Admission|Cgroups|Default Backend|Disable Leader|Endpointslices|Flag|TCP)
The strategy configuration was canceled because "e2e.Ingress_Lua_Memory_Leak_m" failed
unit
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Q8eTaAAAAACoAjsV3WSLQJYzXYZQPag4QkwyQUEyMDMwMTA4MDMzAEVkZ2U=
unit
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
nginx-ingress-e2e-base Expired
248 MB
sha256:0c950bc6abbbb355c0cf8ce3c28d629c4085b20e431ef44252fadb6001146e6c
nginx-ingress-e2e-ctr Expired
90.8 MB
sha256:0c1b0228c50bf1edc95c4937c494f823696c70b8d4cb88a71f2a0483d2c0e636