Has anybody else run the test suite for Py2.3cvs under Mandrake 8.2? I'm seeing some very weird problems, but my komputer karma is running a bit sour today, so I wanted some confirmation. Maybe I should move to Montana soon. Specifically, the first time I ran it earlier today (fresh cvs update, make distclean, configure, make test), the test suite hung in test_linuxaudiodev. Running that test manually also produced a hang. These weren't killable, even with kill -9, C-\, or C-z, and couldn't be gdb attached to. So I rebooted and tried again. This time the tests don't hang but they do fail: test test_linuxaudiodev crashed -- linuxaudiodev.error: (0, 'Error') Hmm. gonna-be-a-mental-toss-flycoon-ly y'rs, -Barry
Specifically, the first time I ran it earlier today (fresh cvs update, make distclean, configure, make test), the test suite hung in test_linuxaudiodev. Running that test manually also produced a hang. These weren't killable, even with kill -9, C-\, or C-z, and couldn't be gdb attached to.
So I rebooted and tried again. This time the tests don't hang but they do fail:
test test_linuxaudiodev crashed -- linuxaudiodev.error: (0, 'Error')
Fred has a good solution for this: chmod 0 /dev/audio --Guido van Rossum (home page: http://www.python.org/~guido/)
Barry A. Warsaw writes:
Not if you still want your audio to work, eh?
That was not a stated requirement. I developed my solution to solve two problems: - linuxaudiodev didn't work for me, but made noise. This seemed to be specific to the sound driver for my laptop. - The audio device made noise. Any application which caused this to happen is clearly buggy, so it had to be disabled. (Obviously I didn't have enough Cravin' Dogs MP3s. ;) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
"Fred" == Fred L Drake, Jr <fdrake@acm.org> writes:
Fred> Barry A. Warsaw writes: >> Not if you still want your audio to work, eh? Fred> That was not a stated requirement. I developed my solution Fred> to solve two problems: Fred> - linuxaudiodev didn't work for me, but made noise. Fred> This seemed to be specific to the sound driver for my Fred> laptop. I actually have no idea if linuxaudiodev will work for me on this machine. It works just fine on my laptop running MD8.1, if you call Guido's screetchy Michael Palin impression "working" <wink>. Fred> - The audio device made noise. Any application which Fred> caused this to happen is clearly buggy, so it had to be Fred> disabled. Near as I can tell, my audio device works just fine, it's Python's linuxaudiodev test under MD8.2 that's broken. Fred> (Obviously I didn't have enough Cravin' Dogs MP3s. ;) Or too much! :) napster-us-all-you-want-baby!-ly y'rs, -Barry
Barry A. Warsaw writes:
Near as I can tell, my audio device works just fine, it's Python's linuxaudiodev test under MD8.2 that's broken.
Err, no... *any* noise from a computer speaker is "broken" in my view. If I wanna hear the Cravin' Dogs, I'll pop a CD in the stereo, or catch a gig. ;-) sooner-cut-the-wires-to-the-speaker-than-let-it-make-noise-ly y'rs, -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
GvR> Fred has a good solution for this:
GvR> chmod 0 /dev/audio
Not if you still want your audio to work, eh?
You didn't mention that. You complained that running the tests froze your audio driver, I believe, and that means that your audio driver is busted -- so leaving the device writable isn't gonna help much. --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (3)
-
barry＠zope.com -
Fred L. Drake, Jr. -
Guido van Rossum