summaryrefslogtreecommitdiff
path: root/README.progress-reporting
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2016-08-12 10:02:28 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2016-08-12 11:12:10 +0200
commit379a36f43d3f4db4afa5ad4fb6f79b89824c999c (patch)
tree03820e0718fe0b888581c1738a61c2c6eba229c2 /README.progress-reporting
parent1cb047079aa2c26a8159d100348b7e69a49bc117 (diff)
ensure a good clock() value for usage and tests
We use clock() as a very cheap way of getting a "random" value, but the manpage warns that this could return -1, so we should be dealing with this. Additionally, e.g. on hurd-i386 the value increases only slowly – to slow for our fast running tests for randomness hence producing the same range in both samples, so we introduce a simple busy-wait loop (as clock is counting processor time used by the program) in the test which delays the second sample just enough making our randomness a bit more predictable.
Diffstat (limited to 'README.progress-reporting')
0 files changed, 0 insertions, 0 deletions