[Bug 40110] New: d3d10core:device and d3d11:d3d11 regression
https://bugs.winehq.org/show_bug.cgi?id=40110 Bug ID: 40110 Summary: d3d10core:device and d3d11:d3d11 regression Product: Wine Version: 1.9.3 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Since the commits below, my fg-acer64 test machine is getting new failures on Windows 8, in both 32 and 64 bits. fg-acer64 is an Acer laptop with an i5-3317U processor and HD Graphics 4000 integrated graphics. d3d10core:device failures: device.c:4858: Test failed: Got unexpected color 0xff0000ff at (0, 0), expected 0xffffffff. device.c:4858: Test failed: Got unexpected color 0xff00ffff at (1, 0), expected 0xff000000. device.c:4858: Test failed: Got unexpected color 0xff00ff00 at (2, 0), expected 0xff000000. device.c:4858: Test failed: Got unexpected color 0xffffff00 at (3, 0), expected 0xff000000. device.c:4858: Test failed: Got unexpected color 0xffff0000 at (0, 1), expected 0xffffff00. device.c:4858: Test failed: Got unexpected color 0xffff00ff at (1, 1), expected 0xff0000ff. device.c:4858: Test failed: Got unexpected color 0xff000000 at (2, 1), expected 0xff00ffff. device.c:4858: Test failed: Got unexpected color 0xff7f7f7f at (3, 1), expected 0x00000000. device.c:4858: Test failed: Got unexpected color 0xffffffff at (0, 2), expected 0xff7f7f7f. device.c:4858: Test failed: Got unexpected color 0xffffffff at (1, 2), expected 0xffff0000. device.c:4858: Test failed: Got unexpected color 0xffffffff at (2, 2), expected 0xffff00ff. device.c:4858: Test failed: Got unexpected color 0xff000000 at (3, 2), expected 0xff7f7f7f. device.c:4858: Test failed: Got unexpected color 0xff000000 at (1, 3), expected 0xffffffff. device.c:4858: Test failed: Got unexpected color 0xff000000 at (3, 3), expected 0x00000000. d3d11:d3d11 failures: d3d11.c:4508: Test failed: Got unexpected color 0xff0000ff at (0, 0), expected 0xffffffff. d3d11.c:4508: Test failed: Got unexpected color 0xff00ffff at (1, 0), expected 0xff000000. d3d11.c:4508: Test failed: Got unexpected color 0xff00ff00 at (2, 0), expected 0xff000000. d3d11.c:4508: Test failed: Got unexpected color 0xffffff00 at (3, 0), expected 0xff000000. d3d11.c:4508: Test failed: Got unexpected color 0xffff0000 at (0, 1), expected 0xffffff00. d3d11.c:4508: Test failed: Got unexpected color 0xffff00ff at (1, 1), expected 0xff0000ff. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (2, 1), expected 0xff00ffff. d3d11.c:4508: Test failed: Got unexpected color 0xff7f7f7f at (3, 1), expected 0x00000000. d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (0, 2), expected 0xff7f7f7f. d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (1, 2), expected 0xffff0000. d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (2, 2), expected 0xffff00ff. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (3, 2), expected 0xff7f7f7f. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (1, 3), expected 0xffffffff. d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (3, 3), expected 0x00000000. The results on test.winehq.org: https://test.winehq.org/data/tests/d3d10core:device.html https://test.winehq.org/data/tests/d3d11:d3d11.html commit 50a8d3f6d2c0bce11aefa94a0b7fa53951d0defe Author: Józef Kucia <jkucia(a)codeweavers.com> Date: Tue Jan 19 22:28:12 2016 +0100 d3d10core/tests: Port test_copy_subresource_region() from d3d11. Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> commit c161543c8678125b00972282208035ad710ff648 Author: Józef Kucia <jkucia(a)codeweavers.com> Date: Tue Jan 19 22:28:11 2016 +0100 d3d11/tests: Add test for ID3D11DeviceContext::CopySubresourceRegion(). Based on test_update_subresource(). Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40110 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source, testcase URL| |https://test.winehq.org/dat | |a/tests/d3d10core:device.ht | |ml Regression SHA1| |50a8d3f6d2c0bce11aefa94a0b7 | |fa53951d0defe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40110 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40110 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia(a)gmail.com --- Comment #1 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to François Gouget from comment #0)
Since the commits below, my fg-acer64 test machine is getting new failures on Windows 8, in both 32 and 64 bits. fg-acer64 is an Acer laptop with an i5-3317U processor and HD Graphics 4000 integrated graphics.
I get a different set of failures when running tests on Windows with Intel HD Graphics 5500. I think this is a 'won't fix'. I'd rather avoid adding a lot of broken cases and/or skips for Windows Intel graphics driver. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40110 --- Comment #2 from Józef Kucia <joseph.kucia(a)gmail.com> --- I've had been looking into various test failures more closely recently. The test failures reported in this bug can be fixed by initializing texture data. I'll send patches soon. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40110 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wine-bugs(a)winehq.org |joseph.kucia(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40110 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |a55c56ee29fccc8e61a0c0cd62e | |b0414607b1567 Status|NEW |RESOLVED Assignee|joseph.kucia(a)gmail.com |wine-bugs(a)winehq.org --- Comment #3 from Józef Kucia <joseph.kucia(a)gmail.com> --- This should be fixed by commit a55c56ee29fccc8e61a0c0cd62eb0414607b1567. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40110 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.9.23. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org