-
Notifications
You must be signed in to change notification settings - Fork 265
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
When freezegun is used at a class level, the pytest durations report shows invalid times #433
Comments
Yeah, can confirm. I've been running into this too, here's my
and with method-level freeze_time:
|
DavidS-cloud
added a commit
to DavidS-cloud/freezegun
that referenced
this issue
Aug 1, 2022
This avoids class-level decorator usage messing with pytest timings. This fixes spulec#433.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's a real example with fake paths illustrating the problem:
1355132.16s
corresponds to over 15 days.I suspect that the pytest durations report logic is relying on
datetime.datetime.now()
which is patched byfreezegun
resulting in the report showing incorrect durations.I don't think this issue is w/in freezegun but it does result in the above reported undesirable side effect.
The text was updated successfully, but these errors were encountered: