| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Fixes test failures caused by using seconds since epoch on Windows, instead
of a box_time_t, and rounding it to the nearest 10^6, which is fine for a
box_time_t (all other platforms), but 10^6 seconds is a rather long time to
ignore changes for on Windows.
This also makes it possible to support subsecond precision on Windows
via FileModificationTime() in future, and have RaidFile detect such subsecond
changes.
|
| |
|
|
|
|
|
|
|
| |
We simulate a 1 second accuracy clock in DEBUG mode on all systems, to help
catch corner cases in tests. This now applies to both RAID and non-RAID files.
We always add file size to the version number to help detect changes,
especially in such cases. In RELEASE builds, we use as much accuracy from the
clock as we can get, as well as file size.
|
| |
|
|
|
|
| |
Hopefully all of these changes are inconsequential.
Merged back changes from the test refactor branch to reduce diffs.
|
| |
|
|
|
| |
64 bits.
|
| |
|
|
|
|
| |
well (e.g. wxWidgets) and it causes conflicts which are difficult to
resolve.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
better on machines which claim to support high-res timestamps but actually
don't (e.g. Linux, MacOS X).
Never do so in debug mode, to help catch problems with the tests failing
to sleep long enough between operations on different connections that
can break caching subtly and randomly.
|
| |
|
|
| |
You may need a new checkout to see this.
|
| | |
|
| | |
|
| |
|
