diff options
| author | Theresa Foley <tfoleyNV@users.noreply.github.com> | 2021-11-11 13:45:23 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-11-11 13:45:23 -0800 |
| commit | 6f523dd95d1f16003c7ed1d4a9e1da0cba0ea76c (patch) | |
| tree | b77a3936db6920d7ad3d6db5e1375197841294e2 /tools/gfx-unit-test/create-buffer-from-handle.cpp | |
| parent | ab8eeeafa2eae54dda78b5fa347bb93c808990f5 (diff) | |
Fix two test cases that were causing problems (#2011)
First, we have a CUDA-only test that simply needed a format name to be changed to match the new conventions in `gfx`.
Second, we have one of the "active mask" tests that seems to produce different results locally for developers (under Vulkan) than it does on CI. This is almost certainly down to differences in GPUs and/or drivers. The inconsistency ultimately proves the point that I was trying to make when I wrote those tests - the "active mask" concept is effectively meaningless as exposed in D3D and Vulkan because it has not been specified in a way that allows programmers to reason about its value, and drivers have implemented wildly different interpretations of its supposed semantics for so long that there is no real hope of turning `WaveGetActiveMask()` into something that returns a well-defined value in any but the most trivial cases.
TLDR: I disabled that test for Vulkan, which means it is completely disabled.
Diffstat (limited to 'tools/gfx-unit-test/create-buffer-from-handle.cpp')
0 files changed, 0 insertions, 0 deletions