-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
--last-failed and --failed-first precedence #2308
Comments
this is a bugfix that would require a major release due to breaking behavior |
I agree that changing the behavior would make more sense and I can't think of a use-case for the existing behavior, so I'm 👍. |
Another +1 from me. If you'd like to have a go at submitting a patch that would be great. |
i submit https://xkcd.com/1172/ for version number considerations ^^ |
Submitted #2357 |
If I run pytest with
--failed-first
and--last-failed
, all tests are run. This is unintuitive for me, since I actually include--failed-first
in mypytest.ini
so it defaults to running failed tests first. However, sometimes I just want to run the failed tests so I add--last-failed
at the commend line, but that has no effect.I think this behaviour should be changed to
--last-failed
taking precedence over--failed-first
.I'd be happy to provide a patch for this if there's an agreement that this is should be changed.
The text was updated successfully, but these errors were encountered: