STINNER Victor victor.stin...@haypocalc.com added the comment:
Oops, I specified the wrong issue number if the commits:
New changeset d3cebbd500aa by Victor Stinner in branch '2.7':
Issue #12250: test_socketserver uses a timeout of 60 seconds instead of 20
Georg Brandl ge...@python.org added the comment:
Can this be closed?
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12550
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
Can this be closed?
I think (hope) that the initial issue (test_socketserver) failure is fixed,
thanks to my second commit.
I'm not complelty satisfied because the traceback was not printed on a SIGALRM
when i tried -m test -F
New submission from STINNER Victor victor.stin...@haypocalc.com:
Sometimes, some tests are stopped because of SIGALRM. A recent example:
---
[157/357] test_socketserver
Alarm clock
*** Error code 142
---
Roundup Robot devnull@devnull added the comment:
New changeset 39873557ff4f by Victor Stinner in branch 'default':
Issue #12550: Add chain optional argument to faulthandler.register()
http://hg.python.org/cpython/rev/39873557ff4f
--
nosy: +python-dev
Roundup Robot devnull@devnull added the comment:
New changeset 30f91fbfc8b3 by Victor Stinner in branch 'default':
Issue #12550: regrtest displays the Python traceback on SIGALRM or SIGUSR1
http://hg.python.org/cpython/rev/30f91fbfc8b3
--
___
Python
STINNER Victor victor.stin...@haypocalc.com added the comment:
My patch doesn't work: the traceback is not printed:
--
$ ./python -m test -v -u network -F test_threadsignals
(...)
[106] test_socketserver
(...)
test_UnixStreamServer
