http://bugs.winehq.org/show_bug.cgi?id=32823
--- Comment #10 from Rico kgbricola@web.de 2013-02-11 14:37:04 CST --- With r600 (2.1 Mesa 9.0.1 or 3.0 Mesa 9.2-devel - cb6470775c0139323bf889d2df2facdbc06a2b09)
Those values are kind of random and fail/succeed from time to time: visual.c:13415: Test succeeded inside todo block: Expected color 0xffff0000 at (80, 100), got 0xffff0000. visual.c:13415: Test succeeded inside todo block: Expected color 0xffff0000 at (240, 100), got 0xffff0000. visual.c:13415: Test succeeded inside todo block: Expected color 0xffff0000 at (80, 450), got 0xffff0000. visual.c:13415: Test succeeded inside todo block: Expected color 0xffff0000 at (240, 450), got 0xffff0000. visual.c:13419: Test failed: Expected color 0xff0000ff at (400, 100), got 0xffff0000. visual.c:13419: Test failed: Expected color 0xff0000ff at (560, 100), got 0xffff0000. visual.c:13419: Test failed: Expected color 0xff0000ff at (400, 450), got 0xffff0000. visual.c:13419: Test failed: Expected color 0xff0000ff at (560, 450), got 0xffff0000. This may look like piglit/fbo-sys-blit error which shows the same behavior here, but I'm not sure if the problem is the same.
Mesa git was build with: LDFLAGS="-m32" CXXFLAGS="-m32" CPPFLAGS="-m32" ./autogen.sh --enable-32-bit --with-dri-drivers="" --with-gallium-drivers="r600,swrast" --enable-texture-float
I couldn't get the errors @visual.c:8717, so it might be intel specific.