fix(ci): run pytest inside .venv to satisfy conftest venv guard#13
Merged
Conversation
The Test (pytest) job installed into the runner's system Python and invoked pytest directly. tests/conftest.py enforces that pytest runs from the project's .venv (exiting 2 otherwise), so CI failed before collecting any tests. Create a .venv in the test job and run install + pytest through it, satisfying the guard's contract without weakening the local-dev safety check (the CUSTODIAN_SKIP_VENV_GUARD escape hatch is left intact). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Test (pytest) job installed into the runner's system Python and
invoked pytest directly. tests/conftest.py enforces that pytest runs
from the project's .venv (exiting 2 otherwise), so CI failed before
collecting any tests.
Create a .venv in the test job and run install + pytest through it,
satisfying the guard's contract without weakening the local-dev safety
check (the CUSTODIAN_SKIP_VENV_GUARD escape hatch is left intact).
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com