Hi all,
there are a number of tests at test.winehq.org that indicate that they're timed out or crashed. The difficulty is, I have no access to machines running the version of Windows on which the test is timing out or failing, and the data about the crash are not helpful in pinpointing the failing test.
How can we get more information about these timeouts/crashes? --Juan
2009/2/11 Juan Lang juan.lang@gmail.com
Hi all,
there are a number of tests at test.winehq.org that indicate that they're timed out or crashed. The difficulty is, I have no access to machines running the version of Windows on which the test is timing out or failing, and the data about the crash are not helpful in pinpointing the failing test.
How can we get more information about these timeouts/crashes? --Juan
i have some of those in my vista pc, in case you can't get to a global
solution i'll be glad to run custom tests that help detect the crashes in my pc, as i'm sure other people will. i understand though that a per machine analysis is not feasible, but it's what i can offer right now.
2009/2/11 Juan Lang juan.lang@gmail.com:
Hi all,
there are a number of tests at test.winehq.org that indicate that they're timed out or crashed. The difficulty is, I have no access to machines running the version of Windows on which the test is timing out or failing, and the data about the crash are not helpful in pinpointing the failing test.
How can we get more information about these timeouts/crashes?
Something like the attached patch?
It needs changes in winetest along with the web dissector to integrate properly, which I haven't got around to doing yet.
-
Juan Lang -
Ricardo Filipe -
Rob Shearman