New submission from Guido van Rossum: I find that test_socket fails regularly (but not always) when run via "regrtest.py -uall". The message is always "socket is not connected" but it's unclear from which test it comes -- all I know is that it comes from tearDown() on line 123.
(This may be a problem with 2.6 as well -- or not.) ---------- components: Tests keywords: easy messages: 62693 nosy: gvanrossum priority: normal severity: normal status: open title: test_socket is flakey type: behavior versions: Python 3.0 __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2163> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
