You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that even though the time is always returned as a floating point number, not all systems provide time with a better precision than 1 second. While this function normally returns non-decreasing values, it can return a lower value than a previous call if the system clock has been set back between the two calls.
Asserting any change in time.time() should not be in the unit tests.
The text was updated successfully, but these errors were encountered:
Our main branch tester failed:
The timestamp appears to stem from:
tribler/src/tribler/core/components/bandwidth_accounting/db/transaction.py
Line 35 in 8d03b99
However, especially on Windows, the granularity of
time.time()
can be bad. In fact, according to the official Python docs:Asserting any change in
time.time()
should not be in the unit tests.The text was updated successfully, but these errors were encountered: