https://bugs.winehq.org/show_bug.cgi?id=54763
--- Comment #5 from Henri Verbeet hverbeet@gmail.com --- (In reply to Simon McVittie from comment #3)
I had wondered about doing that, but went for attachment 74257 [details] instead to try to report the test as skipped, so that people don't get an unrealistic picture of how much coverage vkd3d actually has.
(In practice it still seems to show up as passed rather than skipped in the Autotools test harness, though... perhaps the skipped status isn't getting propagated as a distinctive exit status?)
That's because the shader runner tests get run with a couple of different configurations, and it would be entirely reasonable for e.g. the d3d9 and d3d11 configurations to get run, but not the d3d12 configurations on a particular setup. I think it would make sense to report the test as a SKIP if none of the configurations got run, but we don't currently do that.