-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix stepwise crash when first collected module fails #5446
Fix stepwise crash when first collected module fails #5446
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5446 +/- ##
==========================================
+ Coverage 95.96% 95.98% +0.02%
==========================================
Files 114 114
Lines 25502 25502
Branches 2479 2479
==========================================
+ Hits 24473 24479 +6
+ Misses 723 717 -6
Partials 306 306
Continue to review full report at Codecov.
|
Thanks for providing a failing test @graingert! I implemented and pushed a fix. 👍 |
(We really should initialize all variables during |
Since then pytest itself adopted the behavior of interrupting the test session on collection errors, so --sw no longer needs to handle this. The --sw behavior seems have been implemented when pytest would continue execution even if there were collection errors.
@@ -69,12 +70,6 @@ def pytest_collection_modifyitems(self, session, config, items): | |||
|
|||
config.hook.pytest_deselected(items=already_passed) | |||
|
|||
def pytest_collectreport(self, report): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No longer needed as described in bc345ac.
did this one get backported? hard to tell 🤔 |
It was in 4b104ba |
sweet |
Fix #5444