https://bugs.winehq.org/show_bug.cgi?id=47884
--- Comment #3 from Hans Leidekker hans@meelstraat.net --- (In reply to François Gouget from comment #2)
To diagnose some of these issues it may be useful to modify ok() to print the elapsed time since the start of the test and run the test with WINETEST_REPORT_SUCCESS=1.
If the test has a ton of ok() calls there is a risk that WINETEST_REPORT_SUCCESS slows down the tests even more and causes the timeout by itself. That may be neutralized by an option to only print successful tests if 1 second has elapsed since the last one. Maybe that behavior could be standardized in a WINETEST_REPORT_TIMING option.
I did some tests printing timestamps after each test. There doesn't appear to be a test that takes an inordinate amount of time.
The VM is currently on the vm1 host which has two hard-drives in a non-RAID configuration. On cw-rx460 and cw-gtx560 (i7-2600K+HDD but real hardware) it takes 30s to 38s. On w2008s64 which is on vm2 (slower processor but RAID 0 HDD) it takes ~50s. On wxppro which is on vm3 (faster processor+SSD) it takes 77s. On wvistau64 which is also on vm1 it takes ~108s.
How about replacing the vm1 harddisks with an ssd?