[PATCH 3/3] ddraw/tests: Test P8 to RGB blits (try 2).

[Stefan Dösinger]

As far as I can see those test failures are not caused by my patches. I had a look at them nevertheless.

Am 24.04.2014 um 16:07 schrieb Marvin <testbot at winehq.org>:
> === w864 (32 bit ddraw2) ===
> ddraw2.c:5096: Test failed: Got unexpected refcount 3.
> ddraw2.c:5115: Test failed: Got unexpected refcount 3.
> ddraw2.c:5122: Test failed: Got unexpected hr 0.
> ddraw2.c:5125: Test failed: Got unexpected refcount 3.
> ddraw2.c:5127: Test failed: Got unexpected refcount 2.
> ddraw2.c:5133: Test failed: Got unexpected hr 0.
> ddraw2.c:5136: Test failed: Got unexpected refcount 2.
> ddraw2.c:5138: Test failed: Got unexpected refcount 1.
Apparently Windows 8 assigns the palette to the backbuffer when it is assigned to the frontbuffer.  Apparently this is not true for mipmaps, otherwise the test in patch 2 would have detected it.

According to the data on test.winehq.org this does not happen on all Windows 8 installations though. I think we can accept this behavior with broken()

> === wxppro (32 bit ddraw7) ===
> ddraw7.c:5652: Test failed: Got unexpected palette 00000000, expected 00247AE8.
> ddraw7: unhandled exception c0000005 at 0045EB3B
It’s not obvious from the content of the mail, but apparently the driver refuses to set an 8 bpp display format and consequently refuses to set the palette. If I remember correctly this behavior is new since the testbot outage. Francois, did the graphics driver change? Do you have any new insights into the 8bpp failures on your real hardware and/or the testbot?

I think we should at least change the test to avoid the NULL pointer exception.

> === w864 (32 bit ddraw7) ===
> ...
> ddraw7.c:5790: Test failed: Failed to set cooperative level, hr 0x8876023b.
That’s DDERR_HWNDALREADYSET. Yes, the window was already set, but I don’t see why that’s suddenly an error.

> === w2008s64 (64 bit ddraw7) ===
> ddraw7.c:5652: Test failed: Got unexpected palette 0000000000000000, expected 0000000000802980.
> ddraw7: unhandled exception c0000005 at 0000000000454871
> 
> === w864 (64 bit ddraw7) ===
> ddraw7.c:5652: Test failed: Got unexpected palette 0000000000000000, expected 00000000006BFD90.
> ddraw7: unhandled exception c0000005 at 0000000000454871
> 
> === w864 (32 bit ddraw4) ===
> ...
> ddraw4.c:5920: Test failed: Failed to set cooperative level, hr 0x8876023b.
> ddraw4.c:5959: Test failed: Failed to attach surface, hr 0x887600e1.
> ddraw4.c:5962: Test failed: Got unexpected hr 0.
> ddraw4.c:5964: Test failed: Failed to detach surface, hr 0x887601c2.
> ddraw4.c:5967: Test failed: Failed to attach surface, hr 0x887601c2.
> ddraw4.c:5970: Test failed: Got unexpected hr 0x887601c2.
> ddraw4.c:5972: Test failed: Failed to detach surface, hr 0x887601c2.
> ddraw4.c:5975: Test failed: Failed to attach surface, hr 0x887601c2.
> ddraw4.c:5977: Test failed: Failed to detach surface, hr 0x887601c2.
> ddraw4.c:5980: Test failed: Got unexpected hr 0x887600e1.
> ddraw4.c:5982: Test failed: Got unexpected hr 0x887601c2.
No idea what’s going wrong here. A part of it seems to be that it confuses which surface is attached to which, but there may be more going on. It could be a result of the SetCooperativeLevel failure.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20140424/ba66b8f5/attachment.sig>