Skip to content

CI: run the container mirror job after the VM job hydrated the mirror #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
piob-io merged 1 commit into from
Sep 17, 2026
Merged

CI: run the container mirror job after the VM job hydrated the mirror #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/test-blacksmith.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading