From: Stefan Dösinger stefan@codeweavers.com
---
This must be the longest ignored d3d test failure. I think my r200 GPU does not show this behavior, but my r500 one does. I'll be able to check next week if anyone cares. --- dlls/d3d9/tests/visual.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/dlls/d3d9/tests/visual.c b/dlls/d3d9/tests/visual.c index 23e22c2340f..e70ce7b4b7c 100644 --- a/dlls/d3d9/tests/visual.c +++ b/dlls/d3d9/tests/visual.c @@ -2808,7 +2808,10 @@ static void test_cube_wrap(void) ok(hr == S_OK, "Got hr %#lx.\n", hr);
color = getPixelColor(device, 320, 240); - ok(color_match(color, D3DCOLOR_ARGB(0x00, 0x00, 0x00, 0xff), 1), + /* Modern AMD GPUs do slip into reading the border color. */ + ok(color_match(color, D3DCOLOR_ARGB(0x00, 0x00, 0x00, 0xff), 1) + || broken(color_match(color, D3DCOLOR_ARGB(0x00, 0x00, 0xbf, 0x40), 1) + && address_modes[x].mode == D3DTADDRESS_BORDER), "Got color 0x%08x for addressing mode %s, expected 0x000000ff.\n", color, address_modes[x].name);