Skip to content
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

--failed-first and --new-first don't play well together #12715

Open
Gaelan opened this issue Aug 15, 2024 · 0 comments
Open

--failed-first and --new-first don't play well together #12715

Gaelan opened this issue Aug 15, 2024 · 0 comments

Comments

@Gaelan
Copy link

Gaelan commented Aug 15, 2024

When running pytest --new-first --failed-first, I would expect failing and completely new (ie never run before) tests to run first, then the rest of the test suite in order of modification time. Unfortunately, NFPlugin actually seems to sort the entire test list by modification time, clobbering any ordering done by LFPlugin, so --new-first --failed-first is equivalent to --new-first alone.

Running pytest 8.3.2 on Debian bullseye.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant