[PATCH 3/4] quartz/tests: Check that system clock measurements are in sequence instead of comparing absolute time.
Zebediah Figura (she/her)
zfigura at codeweavers.com
Thu Jul 22 14:34:42 CDT 2021
On 7/22/21 1:59 PM, Francois Gouget wrote:
> On Mon, 19 Jul 2021, Marvin wrote:
>> === w1064v1809 (32 bit report) ===
>> systemclock.c:191: Test failed: Got timestamps 660270000, 660310000, 660270000.
>> === w1064 (32 bit report) ===
>> systemclock.c:191: Test failed: Got timestamps 601610000, 601560000, 601610000.
> It looks like this does fail on about every Windows version, VM or not:
> I guess you're already looking into it?
Yep, it's already on my list.
More information about the wine-devel