[issue17085] test_socket crashes the whole test suite

STINNER Victor added the comment: I believe that my commit 40996d3f6fbd1adcb2e69e426fa311aaf90762ff fixes the root issue in Python 2.7 and so I close the issue. Thanks for the bug report! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed __

[issue17085] test_socket crashes the whole test suite

STINNER Victor added the comment: New changeset 40996d3f6fbd1adcb2e69e426fa311aaf90762ff by Victor Stinner in branch '2.7': bpo-17085: test_socket: cancel scheduled alarm on test failure (#3505) https://github.com/python/cpython/commit/40996d3f6fbd1adcb2e69e426fa311aaf90762ff --

[issue17085] test_socket crashes the whole test suite

STINNER Victor added the comment: Charles-François Natali: > the crash occurs because the test doesn't reset the alarm (with alarm(0)) > upon exit, so if the alarm didn't go off during the test, it comes later when > the original signal handler has been reset, and the default handler just > ex

[issue17085] test_socket crashes the whole test suite

Changes by STINNER Victor : -- pull_requests: +3498 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue17085] test_socket crashes the whole test suite

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue17085] test_socket crashes the whole test suite

Martin Panter added the comment: The patch looks okay to me, to cancel the alarm before removing its signal handler. -- nosy: +martin.panter stage: -> patch review ___ Python tracker _

[issue17085] test_socket crashes the whole test suite

Charles-François Natali added the comment: Thanks for the reminder Mark. Yes, it is probably still an issue with the latest 2.7 release. There were actually two issues: - send send()/sendall() call didn't block because the test doesn't write enough data: we have since added a SOCK_MAX_SIZE cons

[issue17085] test_socket crashes the whole test suite

Mark Lawrence added the comment: Is this still an issue with Python 2.7.8? (I don't have 2.7 or linux to test on) -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue17085] test_socket crashes the whole test suite

ddve...@ucar.edu added the comment: Note that the previous patch would still let the test suite crash if the sendall() takes a short enough time. Having the test suite crash is so bad that I believe this should be the first issue to be fixed! The following patch prevents the test suite from c

[issue17085] test_socket crashes the whole test suite

ddve...@ucar.edu added the comment: The problem is that test_sendall_interrupted and test_sendall_interrupted_with_timeout make an assumption which is false on my hw, namely that it will take a long time for sendall() to complete. In fact, the following snippet: from timeit import default_tim

[issue17085] test_socket crashes the whole test suite

Antoine Pitrou added the comment: ddvento, I'm afraid you'll have to diagnose a bit more by tracing what happens during test_sendall_interrupted and test_sendall_interrupted_with_timeout. These test cases have a legitimate use for arming an alarm signal, but for some reason it seems the signal

[issue17085] test_socket crashes the whole test suite

Etienne Robillard added the comment: since TIPC is silently included in python 2.7.3 and recents kernel memory leaks were found in the linux TIPC kernel code, could this result in info disclosure in python when compiled with TIPC ? does the kernel module needs to be loaded to exploit the memlea

[issue17085] test_socket crashes the whole test suite

ddve...@ucar.edu added the comment: Just to see this test running to completion, I applied the following (ugly) patch: --- Lib/test/test_socket.py.orig2012-04-09 17:07:32.0 -0600 +++ Lib/test/test_socket.py 2013-02-03 06:56:11.778118985 -0700 @@ -14,7 +14,7 @@ import array imp

[issue17085] test_socket crashes the whole test suite

ddve...@ucar.edu added the comment: So I rebuild python withou tipc (basically deleting it from configure, since it cannot be "cleanly" avoided, see Issue17092). The 'sudo modprobe tipc' message of course disappears, but the uncaught alarm is still there, see below: ./python Lib/test/regrtest

[issue17085] test_socket crashes the whole test suite

New submission from ddve...@ucar.edu: While running "make test" on my build of python 2.7.3 the suite aborts with [..omiss..] test_socket make: *** [test] Alarm clock Trying to run individually the offending test reveals a little more $ ./python Lib/test/regrtest.py -v test_socket == CPython