http://bugs.winehq.org/show_bug.cgi?id=29472
--- Comment #16 from marzojr@yahoo.com 2012-02-20 12:46:52 CST --- Created attachment 38990 --> http://bugs.winehq.org/attachment.cgi?id=38990 Log for current git with WINETEST_INTERACTIVE=1 WINEDEBUG=+tid,+timestamp,+alsa,+mmdevapi
Currently, latest release (1.4-rc4) and latest git are identical. It's only this evening that you'll see new commits. What did you use?
I still had wine-1.4-rc2 installed; I now see that 1.4-rc4 is available on the updater.
able to trigger the crash
What crash? You mentioned a lock-up until now.
That is what I meant, sorry. And now that the problem seems to be fixed, I have another bug report to open due to another issue on Regen that was hidden by the lock-up.
In comment #11, you promised a log. You never showed the nature of the 106 test failures.
I should have mentioned sooner that I have been needing to use my computer to compile code and run simulations to meet a deadline, which is why I never posted the log; the deadline is gone now, so I can test this again. Having done the test (using the same revision I used for the earlier tests), I can summarize the log as follows: a diff of the test with the attachments for the 350ms and 750ms logs show that all but the very last line are nearly identical; the last line reports reports 106 failures instead. So the log is useless, as it does not say what failed.
Should I redo it with latest git?
I'd be interested in a log from: cd dlls/mmdevapi/tests; rm /tmp/render.log WINETEST_INTERACTIVE=1 WINEDEBUG=+tid,+timestamp,+alsa,+mmdevapi wine mmdevapi_test.exe.so render >>/tmp/render.log 2>&1 with winecfg or the registry configured to use your working device (if not "default"). Do you hear the test sound with your USB device?
In winecfg, I can hear the test sound; in this test, I can't (but I can hear the USB sound card turning on, it gives off a very faint white noise when it is on). I attached the full log, just in case.