[Python-checkins] Python Regression Test Failures opt (1)
Neal Norwitz
nnorwitz at gmail.com
Tue Oct 9 01:31:02 CEST 2007
On 10/8/07, Brett Cannon <brett at python.org> wrote:
> On 10/8/07, Neal Norwitz <nnorwitz at gmail.com> wrote:
>> [SNIP]
> > test_asynchat
> > WARNING: failed to listen on port 54322, trying another
> > WARNING: failed to listen on port 9907, trying another
> > WARNING: failed to listen on port 10243, trying another
> > WARNING: failed to listen on port 32999, trying another
> > Exception in thread Thread-34:
> > Traceback (most recent call last):
> > File "/tmp/python-test/local/lib/python2.6/threading.py", line 486, in __bootstrap_inner
> > self.run()
> > File "/tmp/python-test/local/lib/python2.6/test/test_asynchat.py", line 22, in run
> > PORT = test_support.bind_port(sock, HOST, PORT)
> > File "/tmp/python-test/local/lib/python2.6/test/test_support.py", line 113, in bind_port
> > raise TestFailed('unable to find port to listen on')
> > TestFailed: unable to find port to listen on
>> Shouldn't the test be skipped instead of considered a failure? It
> isn't asynchat's fault that the test code can't find an open port.
It may not be asynchat's fault (haven't looked), but there is another
test (or asynchat) that isn't cleaning up after itself. I have a fix
for this, I just need to check it in. Probably not tonight. Maybe
tomorrow. It's general, so will fix any test that uses the bind from
test_support.
n
More information about the Python-checkins
mailing list