tschm / pytest-alembic

100%

main: 100%

LAST BUILD ON BRANCH fix/subprocess-sys-executable

branch: fix/subprocess-sys-executable

CHANGE BRANCH

x

Reset

Sync Branches

• fix/subprocess-sys-executable
• build/declare-dependency-floors
• build/declare-tested-python-classifiers
• build/interrogate-docstring-coverage
• build/pin-python-toolchain
• build/pre-commit-and-contributing
• build/replace-m2r2-with-myst-parser
• chore/bump-version-0.13.0
• chore/drop-pytest-asyncio
• chore/drop-python-3.9
• chore/make-ci-pins-real
• ci/cross-platform-tests
• ci/dependency-vuln-scanning
• ci/gate-dependency-floors
• ci/gate-docs-build
• ci/gate-publish-on-tests
• ci/lock-coveralls-deps
• ci/make-matrix-pins-real
• ci/pin-actions-to-shas
• ci/sqlalchemy-range-coverage
• deps/urllib3
• docs/core-api-doctests
• docs/docstring-coverage-100
• docs/fix-broken-fixture-examples
• docs/fix-coverage-badge
• docs/intersphinx-supported-sqlalchemy
• docs/migration-context-size-note
• docs/nitpicky-cross-references
• docs/readme-badges
• fix/collect-outside-rootpath
• fix/collect-test-definitions-default
• fix/deptry-private-pytest-import
• fix/drop-dead-sqlalchemy-asyncio-guard
• fix/lazy-asyncio-import
• fix/previous-revision-base-tautology
• fix/ship-license-in-artifacts
• main
• quality/docs-coverage-and-import-cycle
• refactor/break-package-root-import-cycle
• refactor/split-option-resolver-tests
• test/assert-config-feature-effects
• test/assert-has-test-real-check
• test/coverage-100
• test/drop-asyncio-marker
• test/drop-unused-sqlalchemy-2-marker
• test/gate-doctest-undefined-names
• types/disallow-untyped-defs

Build # 32925565949

Build Type

push

github

Committed by tschm

Commit Message

fix: spawn sys.executable for the collection subprocess, not PATH's python

`get_bare_import_tableset` hard-coded the string "python" as the
interpreter for the clean-import subprocess. That resolves through PATH,
which is not necessarily the interpreter running the tests: under tox, or
any runner that invokes a venv's interpreter by absolute path without
activating it, PATH's python is the system one -- which has no
pytest_alembic installed. On Windows it is frequently not an interpreter
at all.

The child exists to import this very package, so it has to be this
interpreter. The failure mode made that hard to see: a non-zero exit from
the subprocess is caught and re-raised as an AlembicTestFailure, so a
broken environment surfaced as a problem with the user's migrations.

It worked in CI only because setup-uv puts the venv's bin first on PATH.

Closes #201

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Coverage Stats

208 of 208 branches covered (100.0%)

Branch coverage included in aggregate %.

1 of 1 new or added line in 1 file covered. (100.0%)

896 of 896 relevant lines covered (100.0%)

12.0 hits per line