Tor seems to be reading from two different time sources in a macOS VM
I started chutney (and its tors) a few minutes after resuming from sleep, but Tor sometimes gets the time wrong by 15 hours. (Which is approximately the time the VM last slept.)
I wonder if we're using the wrong macOS time APIs? Or it could be a VM or macOS issue.
FAIL: ipv6-exit-min
Detail: chutney/tools/warnings.sh /Users/base/chutney/net/nodes.1532996702
Warning: Couldn't store my own vote! (I told myself, 'Bad valid-after time'.) Number: 2
Warning: Rejecting vote from 127.0.0.1 with valid-after time of 2018-07-31 00:26:05; we were expecting 2018-07-31 00:25:10 Number: 2
Warning: Your system clock just jumped 55189 seconds backward; assuming established circuits no longer work. Number: 3
Warning: Your system clock just jumped 55191 seconds forward; assuming established circuits no longer work. Number: 3
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information