Skip to content

tests: loosen time test, not valid on some systems #2399

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.

Sign up for GitHub

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

Merged
henryiii merged 1 commit into from
Aug 16, 2020
Merged

tests: loosen time test, not valid on some systems #2399

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions tests/test_chrono.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,12 @@ def test_chrono_system_clock():
# The numbers should vary by a very small amount (time it took to execute)
diff = abs(date1 - date2)

# There should never be a days/seconds difference
# There should never be a days difference
assert diff.days == 0
assert diff.seconds == 0

# We test that no more than about 0.5 seconds passes here
# This makes sure that the dates created are very close to the same
# but if the testing system is incredibly overloaded this should still pass
assert diff.microseconds < 500000
# Since datetime.datetime.today() calls time.time(), and on some platforms
# that has 1 second accuracy, we should always be less than 2 seconds.
assert diff.seconds < 2


def test_chrono_system_clock_roundtrip():
Expand Down