http://buildbot.python.org/all/builders/x86%20Gentoo%20Installed%20with%20X%203.x/builds/1004/steps/test/logs/stdio

...
running: test_socket (35311 sec)
running: test_socket (35341 sec)
running: test_socket (35371 sec)
running: test_socket (35401 sec)
running: test_socket (35431 sec)
running: test_socket (35461 sec)
9:54:31 load avg: 2.86 [405/405] test_socket interrupted
sys:1: ResourceWarning: unclosed <socket.socket fd=3, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 38049)>

Zachary Ware killed the test_socket process manually, he owns the buildbot and so has access to it.

The failing build was triggered by the commit 834a5cecac0e77e907762611c06fa460545487e7. Maybe it's related?

Hum, the test passed the following 17 builds.

New failure:

http://buildbot.python.org/all/builders/x86%20Gentoo%20Installed%20with%20X%203.x/builds/1093/steps/test/logs/stdio

...

running: test_socket (238364 sec)
running: test_socket (238394 sec)
running: test_socket (238424 sec)
running: test_socket (238454 sec)
running: test_socket (238484 sec)
running: test_socket (238514 sec)
2 days, 18:18:45 load avg: 0.37 [407/407] test_socket interrupted
sys:1: ResourceWarning: unclosed <socket.socket fd=3, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 38049)>


Test suite interrupted by signal SIGINT.
1 test omitted:
    test_socket
396 tests OK.

10 tests skipped:
    test_asdl_parser test_devpoll test_gdb test_kqueue test_msilib
    test_startfile test_winconsoleio test_winreg test_winsound
    test_zipfile64

Total duration: 3978 min 46 sec
Tests result: INTERRUPTED
program finished with exit code 130
elapsedTime=238725.770805


I guess that Zachary killed again the process.

Zach: Next time, try to send a SIGUSR1 since regrtest installs a signal handler for this signal, to dump the Python traceback. SIGUSR1 doesn't stop the process, it only dumps the traceback. You should send a following SIGINT/SIGTERM to stop the process. But I never tried this, I don't know if it works.

regrtest should do this automatically after TIMEOUT seconds: bpo-30884.

I didn't see the failure recently. I close the issue.

stage: resolved