[codex] Split slow tests from coverage#160
Merged
Merged
Conversation
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.
Summary
--include-slowon Python 3.12--include-slow -m slow --no-cov --durations=20Why
The slow comprehensive tests validate large workload, memory, and end-to-end behavior, but coverage instrumentation makes those generator-heavy tests dramatically slower. Separating the jobs preserves coverage reporting while keeping the slow suite practical for CI.
Validation
uv run pytest --cov-report=xml— 2981 passed, 37 skipped, coverage 79.38%uv run pytest --include-slow -m slow --no-cov --durations=20— 14 passed in 2m36suv run ruff check .uv run ruff format --check .