Message 62693 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	gvanrossum
Recipients	gvanrossum
Date	2008-02-22.17:03:00
SpamBayes Score	0.003187595
Marked as misclassified	No
Message-id	<1203699782.31.0.112043665965.issue2163@psf.upfronthosting.co.za>
In-reply-to

Content
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.)

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.)

History
Date	User	Action	Args
2008-02-22 17:03:02	gvanrossum	set	spambayes_score: 0.00318759 -> 0.003187595 recipients: + gvanrossum
2008-02-22 17:03:02	gvanrossum	set	spambayes_score: 0.00318759 -> 0.00318759 messageid: <1203699782.31.0.112043665965.issue2163@psf.upfronthosting.co.za>
2008-02-22 17:03:01	gvanrossum	link	issue2163 messages
2008-02-22 17:03:00	gvanrossum	create