From e2992b51ada91f198af8ca0bd38a11a6c78a2d5d Mon Sep 17 00:00:00 2001 From: Dan Mihai Date: Tue, 16 Sep 2025 00:23:25 +0000 Subject: [PATCH] tests: k8s-job debug information Log the output of "kubectl logs", to hopefully help understand test failures similar to: https://github.com/kata-containers/kata-containers/actions/runs/17709473340/job/50326984605?pr=11753 not ok 1 Run a job to completion (in test file k8s-job.bats, line 37) `kubectl logs "$pod_name" | grep "$pi_number"' failed Signed-off-by: Dan Mihai --- tests/integration/kubernetes/k8s-job.bats | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/tests/integration/kubernetes/k8s-job.bats b/tests/integration/kubernetes/k8s-job.bats index 9b64d4dec3..605b201cc3 100644 --- a/tests/integration/kubernetes/k8s-job.bats +++ b/tests/integration/kubernetes/k8s-job.bats @@ -19,6 +19,11 @@ setup() { } @test "Run a job to completion" { + local cmd + local logs + local pi_number + local pod_name + # Create job kubectl apply -f "${yaml_file}" @@ -33,8 +38,12 @@ setup() { waitForProcess "$wait_time" "$sleep_time" "$cmd" # Verify the output of the pod + bats_unbuffered_info "Getting logs for $pod_name" + logs=$(kubectl logs "$pod_name") + bats_unbuffered_info "Logs: $logs" + pi_number="3.14" - kubectl logs "$pod_name" | grep "$pi_number" + echo "$logs" | grep "$pi_number" } teardown() {