[Bug 52566] New: d3d11:d3d11 fails in test_clip_distance() on cw-gtx560

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52566

Bug ID: 52566
           Summary: d3d11:d3d11 fails in test_clip_distance() on cw-gtx560
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: directx-d3d
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

d3d11:d3d11 has had failures on cw-gtx560 forever [1] but it recently started
exhibiting a few new failures in test_clip_distance() on cw-gtx560:

d3d11.c:29488: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29054: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29061: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29077: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29089: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29054: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29061: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29077: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29089: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29519: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29054: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29061: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29077: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29089: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29542: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29557: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29569: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.
d3d11.c:29582: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0),
sub-resource 0.

https://test.winehq.org/data/patterns.html#d3d11:d3d11

A bisect shows that these failures started with the same commit that causes
failures on cw-rx460 (see bug 52563):

commit a13fc3bb7e055562b8b9deae985c64c5c7861424
Author: Henri Verbeet 
Date:   Fri Feb 11 19:42:02 2022 -0600

wined3d: Use the chunk allocator for GL vertex buffers.

Signed-off-by: Zebediah Figura 
    Signed-off-by: Henri Verbeet 
    Signed-off-by: Alexandre Julliard

[1] To be fair it got a lot better on 2022-02-09 but sadly these new failures
appeared on a few days later. It's still better than it used to be.

[Bug 52566] d3d11:d3d11 fails in test_clip_distance() on cw-gtx560

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52566

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |regression, source,
                   |                            |testcase
    Regression SHA1|                            |a13fc3bb7e055562b8b9deae985
                   |                            |c64c5c7861424

[Bug 52566] d3d11:d3d11 fails in test_clip_distance() on cw-gtx560

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52566

--- Comment #1 from François Gouget  ---
I have uploaded a WINEDEBUG=+d3d,+d3d11,+d3d_perf log to the URL below:
http://fgouget.free.fr/tmp/d3d11-gtx560.log.xz

[Bug 52566] d3d11:d3d11 fails in test_clip_distance() on cw-gtx560

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52566

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 52566] d3d11:d3d11 fails in test_clip_distance() on cw-gtx560 in Wine

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52566

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|d3d11:d3d11 fails in        |d3d11:d3d11 fails in
                   |test_clip_distance() on     |test_clip_distance() on
                   |cw-gtx560                   |cw-gtx560 in Wine

[Bug 52566] d3d11:d3d11 fails in test_clip_distance() on cw-gtx560 in Wine

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52566

Zeb Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Zeb Figura  ---
The offending machine is out of commission, and I don't see this on any of the
current testbot machines. Is this still reproducible? Can we chalk this up to a
fixed Mesa bug?

[Bug 52566] d3d11:d3d11 fails in test_clip_distance() on cw-gtx560 in Wine

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52566

Zeb Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |ABANDONED

--- Comment #3 from Zeb Figura  ---
(In reply to Zeb Figura from comment #2)
> The offending machine is out of commission, and I don't see this on any of
> the current testbot machines. Is this still reproducible? Can we chalk this
> up to a fixed Mesa bug?

Resolving ABANDONED (hardware no longer available to test with) until this
shows up on any machine again.