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

Don't freeze pytest timings #460

Merged
merged 2 commits into from
Aug 1, 2022
Merged

Conversation

DavidS-cloud
Copy link
Contributor

This avoids class-level decorator usage messing with pytest timings.

This fixes #433.

This avoids class-level decorator usage messing with pytest timings.

This fixes spulec#433.
@DavidS-cloud
Copy link
Contributor Author

I've now deployed this change into our CI, and it has passed and is now keeping more sensible time.

@boxed boxed merged commit ac4d92e into spulec:master Aug 1, 2022
@boxed
Copy link
Contributor

boxed commented Aug 1, 2022

Nice

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

Successfully merging this pull request may close these issues.

When freezegun is used at a class level, the pytest durations report shows invalid times
2 participants