-
Kenton Varda authored
It turns out GetTickCount64() is only precise to the nearest timeslice, which can be up to 16ms. The imprecision caused test failures.
551ab283
It turns out GetTickCount64() is only precise to the nearest timeslice, which can be up to 16ms. The imprecision caused test failures.
Name |
Last commit
|
Last update |
---|---|---|
c++ | Loading commit data... | |
doc | Loading commit data... | |
highlighting | Loading commit data... | |
security-advisories | Loading commit data... | |
.gitignore | Loading commit data... | |
.travis.yml | Loading commit data... | |
CMakeLists.txt | Loading commit data... | |
CONTRIBUTORS | Loading commit data... | |
LICENSE | Loading commit data... | |
README.md | Loading commit data... | |
RELEASE-PROCESS.md | Loading commit data... | |
appveyor.yml | Loading commit data... | |
mega-test-kenton-home.cfg | Loading commit data... | |
mega-test-kenton-work.cfg | Loading commit data... | |
mega-test-quick.cfg | Loading commit data... | |
mega-test.py | Loading commit data... | |
release.sh | Loading commit data... | |
style-guide.md | Loading commit data... | |
super-test.sh | Loading commit data... |