On Wed, Jun 12 @ 16:59, Guido van Rossum wrote:
> I know that there are problem with the two new socket tests:
> test_timeout and test_socket. The problems are varied: the tests
> assume network access and a working and consistent DNS, they assume
> predictable timing, and there is a number of Windows-specific failures
> that I'm trying to track down. Also, when the full test suite is run,
> test_socket.py may hang, while in isolation it will work. (Gosh if
> only we had had these unit tests a few years ago. They bring up all
> sorts of issues that are good to know about.)
>
> I'll try to fix these ASAP.
Yeah, I hadn't gotten around to checking them within the full test
suite. The version I had sent you was just for commentary <grin>. I
try to do as much synchronization as possible. I'm sure fiddling
with the synchronization points in the ThreadableTest class in
test_socket.py will do the trick.
BTW, I've concluded that the unitest module rocks. Just a show
of support here.
-- Mike
--
Michael Gilfix
mgilfix@eecs.tufts.edu
For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4