On Apr 21, 11:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/4/21 William Stein <[EMAIL PROTECTED]>:
<SNIP>
> > Both of the failures you guys report -- in twist.py and testdoc.py involve
> > opening a network port, doing some tests that things are working,
> > then closing it. I think closing just takes a while with ports, perhaps,
> > and that might be relevant. I think if we make the ports in the tests
> > more spread out that could help.
Hi John,
> That makes sense. Would it be better not to report such test failures
> which pass on a second try?
with any doctest failure you should mention if it is reproducible or
not. In this case it seems that twisted or whoever closes the port
might do so in an unclean way, i.e. the kernel considers the port
still open and will only release it after some timeout. Knowing
nothing about the internals of twisted I wouldn't know how to fix it,
so somebody else should dig ;)
> John
>
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
