Repository navigation
Annotate test failures in CI - #106
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
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.
Test failures currently only appear in the CI job log, which makes them hard to find while reviewing a pull request. This adds the pytest-github-actions-annotate-failures plugin to every CI pytest invocation so failures are annotated inline on the diff. The plugin is passed with
--withand stays out of project dependencies and lockfiles.--with=pytest-github-actions-annotate-failuresto the pytest command in thepytest-linuxjobpytest-free-threadedjobpytest-extrasjob