python
runtime_error
ai_generated
partial
AssertionError: assert datetime.datetime(2025, 1, 1, 0, 0) == datetime.datetime(2024, 6, 1, 12, 0)(冻结时间不一致)
AssertionError: assert datetime.datetime(2025, 1, 1, 0, 0) == datetime.datetime(2024, 6, 1, 12, 0)
ID: python/pytest-freeze-time-inconsistent
80%修复率
85%置信度
0证据数
2025-01-14首次发现
版本兼容性
| 版本 | 状态 | 引入 | 弃用 | 备注 |
|---|---|---|---|---|
| 1.4.x | active | — | — | — |
| 1.5.x | active | — | — | — |
根因分析
freezegun 的 freeze_time 未修补 C 扩展中的 datetime,或代码使用 time.monotonic / time.time_ns,而 freezegun 默认不覆盖这些。
English
freezegun's freeze_time doesn't patch datetime in C extensions, or the code uses time.monotonic / time.time_ns which freezegun doesn't override by default.
解决方案
-
85% 成功率
import time from freezegun import freeze_time def test_x(monkeypatch): with freeze_time('2025-01-01'): monkeypatch.setattr(time, 'monotonic', lambda: 0.0) assert run() == expected -
92% 成功率
class Clock: def now(self): return datetime.now(timezone.utc) def test_x(): c = Clock() with freeze_time('2025-01-01'): assert c.now().year == 2025
无效尝试
常见但无效的做法:
-
70% 失败
tick advances time by real elapsed seconds but doesn't patch C-level time functions; the mismatch persists.
-
65% 失败
Module-level freeze doesn't reach C extensions or subprocesses; portions still read the real clock.