Skip to content

ci: let the docker integration lane fail the build #1161

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

Closed
doublewhy wants to merge 1 commit into from
Closed

ci: let the docker integration lane fail the build #1161

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
11 changes: 7 additions & 4 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,12 +117,15 @@ jobs:
- name: Test exact interpreter and clean distribution
run: uv tool run --from 'nox[uv]==2026.4.10' nox -f noxfile.py -s python-compatibility

# Opt-in, non-blocking, runtime-gated container integration tests (RUN-314).
# Kept out of the hermetic `verify` graph; the `docker` marker tests self-skip
# when no runtime is present, and this whole job never fails the build.
# Runtime-gated container integration tests (RUN-314). Kept out of the
# hermetic `verify` graph; the probe step skips the session when no container
# runtime exists (so forks and constrained runners stay green), but when a
# runtime is present -- as on every GitHub-hosted runner -- a failing docker
# integration session fails the build. The reference OCI driver's real
# container IO is exercised only here, so a non-gating lane would leave it
# unguarded.
integration-docker:
runs-on: ubuntu-latest
continue-on-error: true
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
- uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
Expand Down