Call for Help: Fix Win10 test failures
Jeremy White
jwhite at codeweavers.com
Tue Apr 23 08:41:36 CDT 2019
On 4/23/19 7:48 AM, Detlef Riekenberg wrote:
> Microsoft did a lot of changes before or with Win10 Build 16299 (marked as 1709).
>
> This is discovered by a lot more test failures in winetest,
> when compared to the older Win10 Build 10240 on the same machine
> (cw2-gtx560-1709-t64 compared to cw2-gtx560-t64 as an example)
>
>
> Many tests failures look like a more lazy behaviour.
> for application bugs (use after free / use a busy resource)
>
> Please help and fix our tests.
Detlef is my new hero :-).
Cheers,
Jeremy
>
>
>
> Another failure-source is the winetest-failures between different
> Graphics systems (cw1 with a HD6800, cw2 with a gtx560,
> newtb vm with emulated vga/spice and a i7 with an intel HD3000),
> but i didn't look at these yet.
> http://test.winehq.org/data/f9301c2b66450a1cdd986e9052fcaa76535ba8b7/index_Win10.html
>
> The results on the machine "dr-i7*" marked with "not run"
> where removed from winetest-report.
> The full report is here:
> http://test.winehq.org/queue/errw_WDX/report
>
>
> --
> bye bye ...
> ... Detlef
>
>
More information about the wine-devel
mailing list