[Pythonmac-SIG] Other test failures with Py-2.6.5rc1 on OS 10.6.2

[Zvezdan Petkovic]

I can confirm the same test failures on the same platform.
Configured like this:

            ./configure \
                --prefix=${HOME}/opt \
                BASECFLAGS="-arch x86_64 -arch i386" \
                CFLAGS="-arch x86_64 -arch i386" \
                LDFLAGS="-arch x86_64 -arch i386" \
                MACOSX_DEPLOYMENT_TARGET=10.6

The tests were run using:

	~/opt/bin/pythonX.Y -E -tt -m test.regrtest -l -uall

Comments are below.

On Mar 2, 2010, at 3:22 PM, Tom Loredo wrote:
> test_asynchat
> test test_asynchat produced unexpected output:
> **********************************************************************
> error: uncaptured python exception, closing channel <test.test_asynchat.echo_client at 0x1021b6368> (<class 
> 'socket.error'>:[Errno 9] Bad file descriptor [/Volumes/Tracking/Temp-work/Sandbox-installs/Python-
> 2.6.5rc1/Lib/asyncore.py|readwrite|107] [/Volumes/Tracking/Temp-work/Sandbox-installs/Python-
> 2.6.5rc1/Lib/asyncore.py|handle_expt_event|441] [<string>|getsockopt|1] [/Volumes/Tracking/Temp-work/Sandbox-
> installs/Python-2.6.5rc1/Lib/socket.py|_dummy|165])
> ..

This test fails for both Python 2.6.4 and 2.6.5 (32- or 64-bit).
The test passes for Python 2.7 (and, FWIW, for 2.4.6 and 2.5.5)

> test_os
> couldn't allocate two consecutive fds, skipping test_closerange
> /Volumes/Tracking/Temp-work/Sandbox-installs/Python-2.6.5rc1/Lib/os.py:760: DeprecationWarning: integer argument 
> expected, got float
>  bs += read(_urandomfd, n - len(bs))
> ..

These tests pass in the end.  So this is a non-issue.

> 
> 
> test test_smtplib produced unexpected output:
> **********************************************************************
> error: uncaptured python exception, closing channel <test.test_smtplib.SimSMTPChannel 127.0.0.1:57855 at 0x104e7d830> 
> (<class 'socket.error'>:[Errno 9] Bad file descriptor [/Volumes/Tracking/Temp-work/Sandbox-installs/Python-
> 2.6.5rc1/Lib/asyncore.py|readwrite|107] [/Volumes/Tracking/Temp-work/Sandbox-installs/Python-
> 2.6.5rc1/Lib/asyncore.py|handle_expt_event|441] [<string>|getsockopt|1] [/Volumes/Tracking/Temp-work/Sandbox-
> installs/Python-2.6.5rc1/Lib/socket.py|_dummy|165])
> ..

This test fails for both Python 2.6.4 and 2.6.5 (32- or 64-bit).
The test passes for Python 2.7.

> test_tcl
> 2010-03-02 14:36:19.459 python.exe[35793:60b] The application with bundle ID (null) is running setugid(), which is not 
> allowed.
> make: [test] Error 1 (ignored)
> DYLD_FRAMEWORK_PATH=/Volumes/Tracking/Temp-work/Sandbox-installs/Python-2.6.5rc1: ./python.exe -E -tt 
> ./Lib/test/regrtest.py -l 
> ..

This is an interesting one.
Testing stops completely after this failure.
This problem was introduced very recently.

I have Python 2.6.4+ built from Python trunk checkout on February 11.
It passes this test.
Python 2.6.4 and 2.7 also pass this test.

So, the problem was introduced between February 11 and 2.6.5rc1 release.
This is a regression.

	Zvezdan