Preserve rerun status for teardown failures - #367
Open
LouisDeconinck wants to merge 1 commit into
Open
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.
Fixes #366
When a test phase triggers a rerun, a later failed phase from the same attempt must also be reported as a rerun. Previously, a teardown failure after a failed test remained an error even when the rerun passed.
This changes only failed later-phase reports; successful reports keep their existing outcome. Added the issue reproducer, updated the persistent-teardown expectation, and added the required bugfix changelog fragment.
Checks:
uv run pytest -q(217 passed, 9 skipped)uv run --group dev mypy --ignore-missing-imports src/pytest_rerunfailures.pyuv run --with pre-commit pre-commit run --all-filesgit diff --check