[PATCH 3/4] quartz/tests: Check that system clock measurements are in sequence instead of comparing absolute time.

[Francois Gouget]

On Mon, 19 Jul 2021, Marvin wrote:
[...]
> === w1064v1809 (32 bit report) ===
> 
> quartz:
> systemclock.c:191: Test failed: Got timestamps 660270000, 660310000, 660270000.
> 
> === w1064 (32 bit report) ===
> 
> quartz:
> systemclock.c:191: Test failed: Got timestamps 601610000, 601560000, 601610000.

It looks like this does fail on about every Windows version, VM or not:

https://test.winehq.org/data/patterns.html#quartz:systemclock

I guess you're already looking into it?

-- 
Francois Gouget <fgouget at codeweavers.com>