``core.tests.completion_test`` gives inconsistent results. #417
Labels
Comments
It's specific to windows. I think it has something to do with the precision of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While running tests for re-factoring purposes, I've noticed that
core.tests.completion_test
gives inconsistent results over enough subsequent runs. I thought it was something I did, but it does so both on my branch andmaster
. It seems to be just these particular two. I didn't want to slow myself down looking into it, thought maybe there was some known I/O dependency or history here where this was considered acceptable.I think I've seen this both on the windows and linux boxes... these particular results were on a windows machine.
First Run:
Second Run:
Third Run:
The text was updated successfully, but these errors were encountered: