Source: vkd3d Version: 2.0+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: [email protected] User: [email protected] Usertags: ppc64el
Thanks for merging the new upstream release of vkd3d. Unfortunately, the new release fails several of its automated tests in the "tests/d3d12" test-case on ppc64el: https://buildd.debian.org/status/fetch.php?pkg=vkd3d&arch=ppc64el&ver=2.0%2Bds-1&stamp=1784146331&raw=0 If I'm reading the log correctly, the test failures are: >d3d12.c:11416: 84:sat: Test failed: Got {1.00000000e+00, 1.00000000e+00, >1.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, >1.00000000e+00, 0.00000000e+00} at (0, 0). >d3d12.c:11416: 87:min_max: Test failed: Got {1.00000000e+00, nan, >0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, >0.00000000e+00, 0.00000000e+00} at (0, 0). >d3d12.c:11416: 88:min_max: Test failed: Got {0.00000000e+00, nan, >0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, >0.00000000e+00, 0.00000000e+00} at (0, 0). I'm not familiar enough with this codebase and architecture to know whether this is normal for ppc64el, and I don't have any ppc64el hardware myself. Before 2.0, in practice the test suite probably wasn't run at all, because Mesa GL/Vulkan drivers weren't installed - so this test failure might not actually be a regression. If that's the case, then perhaps these three test-cases should be ignored/marked as "todo" on ppc64el for now? smcv
