Skip to content
ccruntime e2e test nightly

ccruntime e2e test nightly #231

Sign in to view logs

ccruntime e2e test nightly

ccruntime e2e test nightly #231

Triggered via schedule August 25, 2024 02:20
@wainersmwainersm
⁠ 0700e2a
main
Status Failure
Total duration 37m 26s
Artifacts –

ccruntime-nightly.yaml

on: schedule
Matrix: e2e-ibm-se-nightly
Matrix: e2e-nightly / operator tests
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 2 warnings
e2e-nightly / operator tests (kata-qemu, ubuntu-22.04)
Testing failed with 2, starting the cleanup...
e2e-nightly / operator tests (kata-qemu, ubuntu-22.04)
Testing failed with 2
e2e-nightly / operator tests (kata-qemu, ubuntu-22.04)
Process completed with exit code 2.
e2e-nightly / operator tests (kata-qemu-sev, sev)
there are ccruntime pods still running
e2e-nightly / operator tests (kata-qemu-snp, sev-snp)
there are ccruntime pods still running
e2e-nightly / operator tests (kata-qemu, ubuntu-20.04)
cc-operator-daemon-install pod is not running
e2e-nightly / operator tests (kata-qemu, ubuntu-20.04)
Testing failed with 1, starting the cleanup...
e2e-nightly / operator tests (kata-qemu, ubuntu-20.04)
there are ccruntime pods still running
e2e-nightly / operator tests (kata-qemu, ubuntu-20.04)
Testing failed with 1
e2e-nightly / operator tests (kata-qemu, ubuntu-20.04)
Process completed with exit code 1.
e2e-nightly / operator tests (kata-qemu, az-ubuntu-2204)
there are ccruntime pods still running
e2e-nightly / operator tests (kata-qemu, az-ubuntu-2004)
there are ccruntime pods still running
e2e-nightly / operator tests (kata-qemu-sev, sev)
Old system's containerd (1.6.8). Configuring the operator to install a newer one
e2e-nightly / operator tests (kata-qemu-snp, sev-snp)
Old system's containerd (1.6.8). Configuring the operator to install a newer one