http://bugs.winehq.org/show_bug.cgi?id=18198
Summary: winetest hangs on or about d3d9:visual Product: Wine Version: 1.1.20 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: testcases AssignedTo: wine-bugs@winehq.org ReportedBy: igoddard@nildram.co.uk
Normally winetest for my system (igoddard-laptop) times out on d3d9:visual but resumes and completes the remaining tests. On 1.1.20 it didn't resume but left the system unresponsive to keyboard. I had to power-cycle to regain control.
http://bugs.winehq.org/show_bug.cgi?id=18198
--- Comment #1 from joaopa jeremielapuree@yahoo.fr 2009-04-24 19:13:44 --- Confirming. For me, it times-out.
http://bugs.winehq.org/show_bug.cgi?id=18198
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2009-04-25 04:34:30 --- No hang here, all completes ok, geforce 8800, 180.44, wine 1.1.20.
http://bugs.winehq.org/show_bug.cgi?id=18198
--- Comment #3 from Ian Goddard igoddard@nildram.co.uk 2009-04-25 05:00:59 --- My platform is Intel 945GM chipset & Ubuntu 8.05.
http://bugs.winehq.org/show_bug.cgi?id=18198
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Alias|d3d9_hangs_winetest | Status|UNCONFIRMED |RESOLVED Component|testcases |-unknown Resolution| |INVALID
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2009-04-25 06:12:00 ---
I had to power-cycle to regain control
That's a sign of buggy video drivers. Report that to your distro developers.
http://bugs.winehq.org/show_bug.cgi?id=18198
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2009-04-25 06:12:38 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=18198
--- Comment #6 from Ian Goddard igoddard@nildram.co.uk 2009-04-27 09:58:15 --- The main point is being missed here.
As winetest works at present it depends on all tests being run before any results can be reported back. If a hung system or a crash in one test prevents this no results from the remaining tests can be made available. At best there are relatively few of us submitting regular winetest reports and I would have thought that test results from a platform with problems would be particularly significant. ISTM that there would be value in looking at a means whereby results from completed tests could be submitted or, even better, a means of restarting at the next test.
As to the cause of the hung system I observed, an "indication" isn't the same thing as proof. And as I've since changed from the i810 driver to the intel driver with no improvement this may be an indication that the problem may lie elsewhere than the driver.
-
wine-bugs＠winehq.org