https://bugs.winehq.org/show_bug.cgi?id=48054
Bug ID: 48054 Summary: gdi32:bitmap fails on Windows XP and 2003 Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
gdi32:bitmap started failing on Windows XP and 2003 right after the winehq.org upgrade:
bitmap.c:1015: Test failed: StretchDIBits failed for 32/62/0/0 bitmap.c:1023: Test failed: GetDIBits failed for 32/62/0/0 bitmap.c:1052: Test failed: StretchDIBits failed for 32/62/0/0 (repeated 12 times)
See http://winetest.dolphin/data/tests/gdi32:bitmap.html See also the attached screenshot showing the failures did start on Sept 09.
And this wine-devel thread: https://www.winehq.org/pipermail/wine-devel/2019-October/152082.html
The failures are systematic and happen on all machines running one of these two Windows versions. What's strange is that the TestBot's wxppro and w2003std VMs have not been modified in this timeframe and neither has the gdi32:bitmap test.
In fact this appears related to the compiler which would explain why the failure started when winehq.org (which builds the official WineTest binaries) was upgraded to Debian 10.
Specifically, letting wtbbuild, which still runs Debian 9.9 (i686-w64-mingw32-gcc 6.3.0 20170516), compile the test binaries results in no failure: https://testbot.winehq.org/JobDetails.pl?Key=59354
But using a binary compiled with i686-w64-mingw32-gcc 8.3-win32 20190406 (in this case on my development machine) produces the 36 failures: https://testbot.winehq.org/JobDetails.pl?Key=59355
Either that or it's quite possibly a result of the new everything-as-PE vs. the old cross-compilation approach still used by wtbbuild.