August 2023 - Wine-Bugs - list.winehq.org

[Bug 55390] d3d9:visual - test_updatetexture() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55390 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.

Aug. 2, 2023

[Bug 55390] New: d3d9:visual - test_updatetexture() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55390 Bug ID: 55390 Summary: d3d9:visual - test_updatetexture() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_updatetexture() fails on w11pro64-amd: visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 12. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 13. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 14. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 15. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 12. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 13. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 14. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 15. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 5. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 7. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 10. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 11. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 12. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 13. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 14. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 15. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 18. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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.

Aug. 2, 2023

[Bug 55389] d3d9:visual - test_per_stage_constant() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55389 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.

Aug. 2, 2023

[Bug 55389] New: d3d9:visual - test_per_stage_constant() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55389 Bug ID: 55389 Summary: d3d9:visual - test_per_stage_constant() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_per_stage_constant() fails on w11pro64-amd: visual.c:20134: Test failed: Got unexpected color 0x000000ff. visual.c:20152: Test failed: Got unexpected color 0x000000ff. visual.c:20170: Test failed: Got unexpected color 0x000000ff. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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.

Aug. 2, 2023

[Bug 55339] d3d9:visual - add_dirty_rect_test() fails on w11pro64_amd and w11pro64_nv

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55339 --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- See bug 55388 for the Nvidia case with the 0x0000ff00 value. -- 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.

Aug. 2, 2023

[Bug 55388] d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55388 --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- Actually the second failure also happens intermittently on w11pro64-nv (Nvidia RTX 3050): visual.c:19792: Test failed: Got unexpected color 0x0000ff00. For instance it happened twice in July: * 2023-07-07 w1121H2_newtb-w11pro64-nv-64 * 2023-07-13 w1121H2_newtb-w11pro64-nv-64 -- 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.

Aug. 2, 2023

[Bug 55388] d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55388 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.

Aug. 2, 2023

[Bug 55388] New: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55388 Bug ID: 55388 Summary: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd: visual.c:19496: Test failed: Failed to draw, hr 0x80004005. visual.c:19792: Test failed: Got unexpected color 0x0000ff00. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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.

Aug. 2, 2023

[Bug 55387] d3d9:visual - test_fetch4() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55387 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.

Aug. 2, 2023

[Bug 55387] New: d3d9:visual - test_fetch4() fails on w11pro64-amd

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55387 Bug ID: 55387 Summary: d3d9:visual - test_fetch4() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_fetch4() fails on w11pro64-amd: visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff131313 at (40, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff121212 at (200, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff111111 at (360, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff101010 at (520, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff020202 at (40, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff2f2f2 at (200, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff1f1f1 at (360, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff010101 at (520, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff040404 at (40, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff4f4f4 at (200, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff3f3f3 at (360, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff030303 at (520, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff232323 at (40, 390). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff222222 at (200, 390). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff212121 at (360, 390). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff202020 at (520, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (520, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 150). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 150). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 150). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (520, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (520, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff131313 at (40, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff121212 at (200, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff111111 at (360, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff101010 at (520, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff020202 at (40, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff2f2f2 at (200, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff1f1f1 at (360, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff010101 at (520, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff040404 at (40, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff4f4f4 at (200, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff3f3f3 at (360, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff030303 at (520, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff232323 at (40, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff222222 at (200, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff212121 at (360, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff202020 at (520, 390). See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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.

Aug. 2, 2023