[Python-bugs-list] [ python-Bugs-451636 ] make test caused machine hangup

[noreply@sourceforge.net]

Bugs item #451636, was opened at 2001-08-16 10:27
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=451636&group_id=5470

Category: Build
Group: Python 2.1.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: make test caused machine hangup

Initial Comment:
OS and Python versions:
Linux turb 2.2.17-8enterprise #1 SMP Fri Nov 17
16:02:20 EST 2000 i686 unknown

Python 2.1.1 (#1, Aug 15 2001, 16:39:55) 
[GCC 2.96 20000731 (Red Hat Linux 7.0)] on linux2

In following the standard procedure:

./configure
make
make test

our RedHat machine locked up when testing
linuxaudiodev.

The speaker on the machine was uttering nonsense
repeatedly. We had to reboot the machine and run fsck
to clear things up.

Thanks,

Gerry Wiener
National Center for Atmospheric Research
gerry@ucar.edu



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-08-16 12:35

Message:
Logged In: NO 

Our version of Red Hat was factory installed at Dell on a
Dell PC. Admittedly there may be a problem with how the OS
was configured or with the sound card. Still, I would think
"make test" would be more user friendly if:

1. Testing linuxaudiodev be optional -- perhaps make
test_optional. 

2. Warnings be provided with regard to make test in the
README file, i.e., some users have experienced system
crashes when using make test owing to problems with
linuxaudiodev.

Note that we typically are not interested in the use of the
sound cards on our systems -- our systems are generally used
for running scientific algorithms.  

Gerry Wiener
gerry@ucar.edu




----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2001-08-16 11:33

Message:
Logged In: YES 
user_id=21627

Why do you think this is a Python bug? Python was acessing 
the hardware of your computer through the official 
interfaces that your operating system offers for that. 
Unless you can demonstrate that it did wrong doing so, 
I'll assume that either your machine is misconfigured, or 
the sound drivers of your system are broken. In that case, 
you best disable sound support, since it won't work 
anyways.

Since the specific test works without problems on any 
other Linux system, I propose to close this bug as "Works 
for me".


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=451636&group_id=5470