Skip to content
ci-test-ginkgo

fix: handle pod deletion in kubearmor controller #4634

Sign in to view logs

fix: handle pod deletion in kubearmor controller

fix: handle pod deletion in kubearmor controller #4634

Triggered via pull request February 5, 2025 10:05
@Aryan-sharma11Aryan-sharma11
synchronize #1952
Aryan-sharma11:fix-pod-deletion
Status Failure
Total duration 35m 2s
Artifacts 1

ci-test-ginkgo.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 4 warnings
Auto-testing Framework / ubuntu-20.04 / crio
Process completed with exit code 1.
Auto-testing Framework / ubuntu-20.04 / crio
Process completed with exit code 2.
Auto-testing Framework / ubuntu-20.04 / containerd
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Auto-testing Framework / ubuntu-20.04 / containerd
Process completed with exit code 2.
Auto-testing Framework / ubuntu-20.04 / containerd
Process completed with exit code 1.
Auto-testing Framework / ubuntu-20.04 / crio
No files were found with the provided path: KubeArmor/coverage_k8s_ubuntu-20.04_crio.out. No artifacts will be uploaded.
Auto-testing Framework / ubuntu-20.04 / crio
Restore cache failed: Dependencies file is not found in /home/runner/work/KubeArmor/KubeArmor. Supported file pattern: go.sum
Auto-testing Framework / ubuntu-20.04 / containerd
Restore cache failed: Dependencies file is not found in /home/runner/work/KubeArmor/KubeArmor. Supported file pattern: go.sum
Auto-testing Framework / ubuntu-20.04 / containerd
No files were found with the provided path: KubeArmor/coverage_k8s_ubuntu-20.04_containerd.out. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size
kubearmor.logs
429 KB