As pointed out by Zeb on !3565 there was a real bug behind this test: https://bugs.winehq.org/show_bug.cgi?id=45932 . I think the problem was accidental filling of the GPU submission queues, which usually won't be done with a few hundred loops.
Sure, but it's not worth spending 60s on it.
The test isn't slow on proper GPUs, the 30k iterations take 0.5 seconds on my system. If we care about speed in the d3d tests we shouldn't use a software renderer.
No, we should simply skip that test if the renderer is too slow, which is what I suggested.