afonso/core-extra
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

updated usage of time.time to time.monotonic or time.perf_counter due to time.time possibly rolling backwards

Browse source
This commit is contained in:
Blake Harnden 2019-12-06 09:42:41 -08:00
parent b9bbf397c9
commit 45a23a6c14
11 changed files with 29 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

2
daemon/tests/test_grpc.py
View file

@ -1042,7 +1042,7 @@ class TestGrpc:
client.events(session.id, handle_event)
time.sleep(0.1)
event = EventData(
event_type=EventTypes.RUNTIME_STATE.value, time=str(time.time())
event_type=EventTypes.RUNTIME_STATE.value, time=str(time.monotonic())
)
session.broadcast_event(event)

2
daemon/tests/test_gui.py
View file

@ -523,7 +523,7 @@ class TestGui:
MessageFlags.ADD.value,
[
(EventTlvs.TYPE, EventTypes.SCHEDULED.value),
(EventTlvs.TIME, str(time.time() + 100)),
(EventTlvs.TIME, str(time.monotonic() + 100)),
(EventTlvs.NODE, node.id),
(EventTlvs.NAME, "event"),
(EventTlvs.DATA, "data"),