Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Python: Bugs

test_signal hangs when running as part of testall (PR#288)

 

 

Python bugs RSS feed   Index | Next | Previous | View Threaded


kessler at ccdc

Apr 11, 2000, 3:58 AM

Post #1 of 2 (56 views)
Permalink
test_signal hangs when running as part of testall (PR#288)

Full_Name: Magnus Kessler
Version: 1.6a2
OS: Irix6.3
Submission from: chilli.mcc.wwwcache.ja.net (194.83.240.17)


Under Irix6.3 (python compiled in -n32 mode with MipsPro 7.2.1), test_signal
works fine (?) if you run it on its own:

>>> import test.test_signal
starting pause() loop...
call pause()...
+ kill -5 7487
+ sleep 2
handlerA (5, <frame object at 100cf928>)
pause() returned
call pause()...
+ kill -2 7487
+ sleep 2
handlerB (2, <frame object at 100cf928>)
HandlerBCalled exception caught
call pause()...
+ kill -3 7487
KeyboardInterrupt (assume the alarm() went off)

however, as part of the test suite, this test hangs:

>>> import test.testall
[...]
test_signal
test_signal
+ sleep 2
starting pause() loop...
call pause()...
+ kill -5 7454
+ sleep 2
+ kill -2 7454
+ sleep 2
+ kill -3 7454


guido at python

Apr 11, 2000, 8:24 AM

Post #2 of 2 (56 views)
Permalink
Re: test_signal hangs when running as part of testall (PR#288) [In reply to]

> Under Irix6.3 (python compiled in -n32 mode with MipsPro 7.2.1), test_signal
> works fine (?) if you run it on its own:
>
> >>> import test.test_signal
> starting pause() loop...
> call pause()...
> + kill -5 7487
> + sleep 2
> handlerA (5, <frame object at 100cf928>)
> pause() returned
> call pause()...
> + kill -2 7487
> + sleep 2
> handlerB (2, <frame object at 100cf928>)
> HandlerBCalled exception caught
> call pause()...
> + kill -3 7487
> KeyboardInterrupt (assume the alarm() went off)
>
> however, as part of the test suite, this test hangs:
>
> >>> import test.testall
> [...]
> test_signal
> test_signal
> + sleep 2
> starting pause() loop...
> call pause()...
> + kill -5 7454
> + sleep 2
> + kill -2 7454
> + sleep 2
> + kill -3 7454

Yes, I've seen this too. Unfortunately, I don't have a clue, and I
don't have the time to delve into it... I bet there's a compile time
#define that might do it. It may have something to do with threads...

--Guido van Rossum (home page: http://www.python.org/~guido/)

Python bugs RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.