From c7147dabceea32246a3eaa10b6f19aa320e99f00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Tue, 12 Sep 2023 16:13:00 +0200 Subject: [PATCH] ci: docker: Run the tests after the kata-static is created MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit There's no reason to wait till the payload is created to run the tests, as we rely on the tarball, not on the kata-deploy payload. That was a mistake on my side, and that's already fixed for the nerdctl tests. Signed-off-by: Fabiano Fidêncio (cherry picked from commit c83f167c5981a5c043dd2d3dcbcaa5f333e353bc) --- .github/workflows/ci.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 8f7c90ffb..8b8ad8ab4 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -74,7 +74,7 @@ jobs: file: tests/integration/kubernetes/runtimeclass_workloads/confidential/unencrypted/Dockerfile run-docker-tests-on-garm: - needs: publish-kata-deploy-payload-amd64 + needs: build-kata-static-tarball-amd64 uses: ./.github/workflows/run-docker-tests-on-garm.yaml with: tarball-suffix: -${{ inputs.tag }}