test_timeout(): This test was added during Bug Day, but disabled
soon after because the gmail address it connects to started timing
out on all the buildbot slaves. Rewrote the test to produce a
warning message (instead of failing) when the address times out.
Also removed the special case for Windows -- this test started to
work on Windows as soon as bug 1462352 was fixed.
In some environments (under screen, in a chroot) curses doesn't support
mouse events. This makes the test fail. Catch that case and don't run
the tests. Should make the debian/ubuntu buildbots that run in a chroot
work again.
Fix test_pty on OSF/1 (Tru64). The problem is that the newline gets
converted to CR CR NL. There may be a way to fix this with tcsetattr,
but I couldn't find it. There was a similar problem on IRIX.
Just normalize the output and compare that.
test_timeout(): Disable this new test on all platforms.
The
s.connect(("gmail.org", 995))
line has been timing out on all buildbot slaves for hours
now, causing the test to fail.
unicode_escape and raw_unicode_escape codec now encodes backslash correctly.
This caused another issue for unicode repr strings being double-escaped
(SF Bug #1459029). Correct fix will be in 2.5, but is too risky for 2.4.3.
Added a testcase for #1459029.
Try to repair at least one segfault on the Mac buildbot,
as diagnosed by Nick Coghlan.
test_capi.py: A test module should never spawn a thread as
a side effect of being imported. Because this one did, the
segfault one of its thread tests caused didn't occur until
a few tests after test_regrtest.py thought test_capi was
finished. Repair that. Also join() the thread spawned
at the end, so that test_capi is truly finished when
regrtest reports that it's done.
_testcapimodule.c test_thread_state(): this spawns a
couple of non-threading.py threads, passing them a PyObject*
argument, but did nothing to ensure that those threads
finished before returning. As a result, the PyObject*
_could_ (although this was unlikely) get decref'ed out of
existence before the threads got around to using it.
Added explicit synchronization (via a Python mutex) so
that test_thread_state can reliably wait for its spawned
threads to finish.
Move registration of the codec search function to the module scope
so it is only executed once. Otherwise the same search function is
repeated added to the codec search path when regrtest is run with -R
and leaks are reported.
Handle sys.getfilesystemencoding() returning None.
ascii seems like the safest bet, it should exist. I wonder if utf-8
would be a better choice? This should get test_fileinput passing on OpenBSD.
patch from the trunk.
This stops test_socket_ssl from dying with:
TypeError: 'NoneType' object is not callable
in urlparsre.py's urljoin() when the tests are run in this order:
test_???
test_importhooks
test_socket_ssl
"test_???" can be various things, but must be there. For
example, test_urllibnet "works" to provoke the failure.
Alas, nobody actually understands _why_ test_socket_ssl fails
then, or why this hack makes the problem go away.
Amazingly, the tests just happened to run in the right order on
the 2.4 branch on two Windows buildbot slaves today, causing them
both to fail their most recent test runs before this patch.
"""
Try to find a host that responds slower from python.org so this test
does not fail on macteagle (G4 OSX.4 in buildbot)
"""
Since testConnectTimeout() frequently fails in the same way in 2.4
branch, and this patch seems to have fixed it on the trunk, it
should fix it on the 2.4 branch too.
on a box without a sound card.
Update test_winsound to check for a configured sound card (using a VBScript
helper written by Roger Upole and Mark Hammond) and adjust the expected
PlaySoundTest case results accordingly.
Try to be a bit more consistent on all platforms:
python .
python < .
both print a message, return non-zero and do not core dump.
This hopefully fixes the failure on Solaris.
