From f64075eaa4751061f0251064b88a374664d3155e Mon Sep 17 00:00:00 2001 From: piotr Date: Thu, 17 Sep 2026 13:00:10 +0000 Subject: [PATCH] CI: run the container mirror job after the VM job hydrated the mirror Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- .github/workflows/test-blacksmith.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/test-blacksmith.yml b/.github/workflows/test-blacksmith.yml index d2c24d3..b6019d6 100644 --- a/.github/workflows/test-blacksmith.yml +++ b/.github/workflows/test-blacksmith.yml @@ -133,8 +133,14 @@ jobs: # may hydrate the mirror. When no hydrated mirror exists yet, PR runs are # sent down the direct-checkout fallback; they verify that fallback and # report the mirror assertions as skipped instead of failing. + # + # Runs after the VM job: while one job hydrates a fresh mirror entity, the + # backend answers concurrent requests with "hydration in progress" and those + # jobs clone directly, so a container job started alongside the VM job would + # miss the mirror whenever the entity was new (first push after a purge). test-git-mirror-container: runs-on: blacksmith + needs: test-git-mirror container: image: ubuntu:24.04 options: --privileged -v /dev:/dev