Why is that? We'll fail to create unimplemented command list types, but we have todo_wine for that.
Mmh, even on Windows trying to create a command queue on any type other than `DIRECT`, `COMPUTE` or `COPY` fails with `E_INVALIDARG`.
Looking at the docs, I think that `D3D12_COMMAND_LIST_TYPE_BUNDLE` is not supposed to be passed to `CreateCommandQueue()` but to `CreateCommandList()`, so makes no sense here. The other possible values are for video decoding/encoding, which is (AFAIK) completely unsupported on Wine anyway, so it would make little sense to check that queue creation works. I suppose it fails on the testbot because it misses some configuration/support.
All in all, I think that these two are the things it makes sense to test anyway, so it is the comment that has to be deleted.
It might not be a bad idea to test command list types that are supposed to succeed as well, to avoid the CreateSwapChain() call failing due to e.g. an unsupported swapchain_desc parameter.
Creating a swap chain on a direct command queue is already well tested in many other places. Here I think it would complicate the control flow without adding much useful signal.