Unit tests for time.Clock.get_time()

[pedrodelapena]

Closes #1787

[MyreMylar]

This test currently takes 3 minutes to run on it's own, that's longer than all the other tests combined.

The problem with that is that since the CI on Appveyor runs each build in sequence... well it basically triples the amount of time the CI takes to run and (as I discovered before when I enabled /analyze on every build). Appveyor can quickly get backed up on busy days with multiple pull requests waiting to have their go.

I think the time delay needs to be reduced a lot to something like:

time.sleep(.100)

then the test should be more like 3 seconds long and should still achieve the same goal.

Thanks for the contribution!

[MyreMylar]

I'm slightly nervous about reducing the error delta as we just had two time module tests fail on CI today because their timing error delta was too small - but perhaps it'll be fine.

[pedrodelapena]

I'm slightly nervous about reducing the error delta as we just had two time module tests fail on CI today because their timing error delta was too small - but perhaps it'll be fine.

I'll revert the changes on the delta parameter and I'll squash the commits. The error delta I originally used was too small while the delay I used was too big, which lead me to increase the first later on. I hope this change gets it all right!

[MyreMylar]

LGTM 👍

[illume]

Thanks :)