A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-September/017512.html below:

[Python-Dev] test_socketserver fails

[Python-Dev] test_socketserver failsJeremy Hylton jeremy@zope.com
Mon, 17 Sep 2001 13:50:42 -0400 (EDT)
>>>>> "GvR" == Guido van Rossum <guido@python.org> writes:

  >> Python 2.2a3+ (#336, Sep 17 2001, 12:56:00) [GCC 2.95.2 19991024
  >> (release)] on linux2 Type "help", "copyright", "credits" or
  >> "license" for more information.
  >> >>> import test.test_socketserver

  GvR> I believe that's the problem.  The import lock gets in the way.
  GvR> Try running it from the command line:

  GvR> python Lib/test/test_socketserver.py

Aha!  Then the code at the top is really broken:

# XXX This must be run manually -- somehow the I/O redirection of the
# regression test breaks the test.

from test_support import verbose, verify, TESTFN, TestSkipped
if not verbose:
    raise TestSkipped, "test_socketserver can only be run manually"

There are two substantial problems.  First, the comment about I/O
redirection is wrong.  Second, if you do run regrtest.py -v, then the
test will be run anyway.  This is how I first stumbled over the
problem.  Another test was failing and I used -v to figure out why.
But regrtest.py also reported that test_socketserver failed and then
hung, because socketserver non-daemon threads were still running.

So what's the right way to fix this test?  If the test can't be run as
part of regrtest and can't be imported, I wonder why it's in Lib/test
to begin with.

Jeremy






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