https://bugs.winehq.org/show_bug.cgi?id=35579
--- Comment #3 from Henri Verbeet hverbeet@gmail.com --- (In reply to comment #2)
So there are two impacted drivers:
- The VMware SVGA 3D 7.14.1.5025 (2013/12/7) driver. (as well as the older 7.14.1.1134 (2011/11/11) one).
- The Intel HD4000 10.18.10.3345 (2013/10/31) driver. (the corresponding driver download is tagged as 15.33.8.64.3345
presumably it's a bundle with the audio driver)
If it's valid but unwanted behavior then it MUST be tagged as broken() rather than left to fail.
Well, there isn't any public spec for this, or most parts of the Win32 API really, so in that regard it's always hard to say what's valid and what isn't. What we've always cared about is applications, and failing these tests means breaking them. For example, exp_test is for bug 27850, and IIRC failing the rcp and rsq ones would break Battlefield 1942.
If it's a driver bug then it should really be reported so it's fixed and we don't have to deal with this failure forever. The report should be made by someone who will be able to answer technical questions, know which applications are impacted, etc. (so definitely not me).
I wish anyones who wants to try that good luck, but my experience it pretty much that if you want something fixed you need to do it yourself, with very few exceptions.
That leaves the question of what to do until the drivers are fixed. This impacts more than just the WineTestBot. I'm trying to get my laptop under the new 50 failing tests limit and while one test is not an issue, it would not do to leave the 40 DirectX/OpenGL tests to fail just because a very maintream driver is buggy. Also even one failure means no green for Windows 8 on the test.winehq.org results, which in turns makes it harder to know when there are new failing tests.
Every time I write a new test, it seems more and more tempting to either just skip the D3D tests completely on anything that isn't AMD or NVIDIA, or to just stop writing new tests.