Hi,
on my XP machine the visual d3d9 test produces a timeout message, when it is started from the winetest build. Anyone here could run the tests on windows without a timeout (and off course without skipping half of the tests - have to be more than 4k tests)?
Also there is no message about a timeout on the test site ( http://test.winehq.org/data/028617b90ba586bdb30723c700eea888c159ada7/xp_rs-x... ).
Cheers Rico
On Tue, Dec 23, 2008 at 9:57 PM, Rico Schüller kgbricola@web.de wrote:
Hi,
on my XP machine the visual d3d9 test produces a timeout message, when it is started from the winetest build. Anyone here could run the tests on windows without a timeout (and off course without skipping half of the tests - have to be more than 4k tests)?
Also there is no message about a timeout on the test site ( http://test.winehq.org/data/028617b90ba586bdb30723c700eea888c159ada7/xp_rs-x... ).
Cheers Rico
While it's true that it takes some time and says it timed out while running and will attempt to terminate it when you hit OK, I think this dialog appears while the test is still running you don't notice it until after it successfully finishes and exits, so the attempt to terminate does nothing.
I have seen this happen on Windows 2008 with GeForce 8 (180.42) and Windows 98 with GeForce 5.
-Jeff
Jeff Zaroyko wrote:
On Tue, Dec 23, 2008 at 9:57 PM, Rico Schüller kgbricola@web.de wrote:
Hi,
on my XP machine the visual d3d9 test produces a timeout message, when it is started from the winetest build. Anyone here could run the tests on windows without a timeout (and off course without skipping half of the tests - have to be more than 4k tests)?
Also there is no message about a timeout on the test site ( http://test.winehq.org/data/028617b90ba586bdb30723c700eea888c159ada7/xp_rs-x... ).
Cheers Rico
While it's true that it takes some time and says it timed out while running and will attempt to terminate it when you hit OK, I think this dialog appears while the test is still running you don't notice it until after it successfully finishes and exits, so the attempt to terminate does nothing.
I have seen this happen on Windows 2008 with GeForce 8 (180.42) and Windows 98 with GeForce 5.
My Atom based netbook with i915 graphics on F10 hits the timeout too. It's a minor nuisance as I have to hit the "OK" button even though the test will finish just fine.
bye michael
Michael Stefaniuc schrieb:
Jeff Zaroyko wrote:
On Tue, Dec 23, 2008 at 9:57 PM, Rico Schüller kgbricola@web.de wrote:
Hi,
on my XP machine the visual d3d9 test produces a timeout message, when it is started from the winetest build. Anyone here could run the tests on windows without a timeout (and off course without skipping half of the tests - have to be more than 4k tests)?
Also there is no message about a timeout on the test site ( http://test.winehq.org/data/028617b90ba586bdb30723c700eea888c159ada7/xp_rs-x...
).
Cheers Rico
While it's true that it takes some time and says it timed out while running and will attempt to terminate it when you hit OK, I think this dialog appears while the test is still running you don't notice it until after it successfully finishes and exits, so the attempt to terminate does nothing.
I have seen this happen on Windows 2008 with GeForce 8 (180.42) and Windows 98 with GeForce 5.
My Atom based netbook with i915 graphics on F10 hits the timeout too. It's a minor nuisance as I have to hit the "OK" button even though the test will finish just fine.
bye michael
Thanks for the answers, so nothing to worry about, it's just a little bit annoying.
Cheers Rico
My Atom based netbook with i915 graphics on F10 hits the timeout too. It's a minor nuisance as I have to hit the "OK" button even though the test will finish just fine.
Maybe its time to split the d3d9 visual tests up. There are so many tests in there, which often have little in common appart of the comparably small framework for visual tests.
On a properly working machine the tests run in just a second or less, but some drivers(even on Windows) are pretty slow in GetFrontBufferData. That may be the reason for the timeout.