[PATCH 2/2] d3dx9/tests: Add a mesh test for D3DXCreateBox()

[Matteo Bruni]

u2014-02-27 12:19 GMT+01:00 Marvin <testbot at winehq.org>:
> Hi,
>
> While running your changed tests on Windows, I think I found new failures.
> Being a bot and all I'm not very good at pattern recognition, so I might be
> wrong, but could you please double-check?
> Full results can be found at
> https://newtestbot.winehq.org/JobDetails.pl?Key=5232
>
> Your paranoid android.
>
>
> === w8 (32 bit mesh) ===
> mesh.c:8156: Test failed: Mesh 27: new_num_vertices == 6, expected 4.
> mesh.c:8170: Test failed: Mesh 27: indices[3] == 3, expected 1
> mesh.c:8170: Test failed: Mesh 27: indices[4] == 4, expected 3
> mesh.c:8170: Test failed: Mesh 27: indices[5] == 5, expected 2
> mesh.c:8211: Test failed: Mesh 27: vertex_remap_ptr[3] == 3, expected 4
> mesh.c:8211: Test failed: Mesh 27: vertex_remap_ptr[4] == 4, expected -1
> mesh.c:8211: Test failed: Mesh 27: vertex_remap_ptr[5] == 5, expected -1
> mesh.c:8226: Test failed: Mesh 27: Got (2.000000, 3.000000, 0.000000) for vertex 3 position, expected (3.000000, 0.000000, 0.000000).
>

FWIW, this test failure is unrelated to the patch. I see it's failing
inconsistently on Win8, while e.g. it doesn't fail for me on Win7. As
far as I understand, it's the float color vertex data the culprit
(i.e. native d3dx9 doesn't really handle that case and the test passes
or fails "by luck").
I'm going to send a patch for that.