Mailman 3 April 2008 - Python-checkins

buildbot failure in S-390 Debian 3.0
by buildbot＠python.org 04 Apr '08

04 Apr '08

The Buildbot has detected a new failure of S-390 Debian 3.0. Full details are available at: http://www.python.org/dev/buildbot/all/S-390%20Debian%203.0/builds/191 Buildbot URL: http://www.python.org/dev/buildbot/all/ Buildslave for this Build: klose-debian-s390 Build Reason: Build Source Stamp: [branch branches/py3k] HEAD Blamelist: thomas.heller BUILD FAILED: failed test Excerpt from the test logfile: 1 test failed: test_signal make: *** [buildbottest] Error 1 sincerely, -The Buildbot

1 0

buildbot failure in x86 XP-3 3.0
by buildbot＠python.org 04 Apr '08

04 Apr '08

The Buildbot has detected a new failure of x86 XP-3 3.0. Full details are available at: http://www.python.org/dev/buildbot/all/x86%20XP-3%203.0/builds/757 Buildbot URL: http://www.python.org/dev/buildbot/all/ Buildslave for this Build: heller-windows Build Reason: Build Source Stamp: [branch branches/py3k] HEAD Blamelist: thomas.heller BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

buildbot failure in g4 osx.4 3.0
by buildbot＠python.org 04 Apr '08

04 Apr '08

The Buildbot has detected a new failure of g4 osx.4 3.0. Full details are available at: http://www.python.org/dev/buildbot/all/g4%20osx.4%203.0/builds/694 Buildbot URL: http://www.python.org/dev/buildbot/all/ Buildslave for this Build: psf-g4 Build Reason: Build Source Stamp: [branch branches/py3k] HEAD Blamelist: thomas.heller BUILD FAILED: failed test Excerpt from the test logfile: 1 test failed: test_signal make: *** [buildbottest] Error 1 sincerely, -The Buildbot

1 0

buildbot failure in sparc Ubuntu trunk
by buildbot＠python.org 04 Apr '08

04 Apr '08

The Buildbot has detected a new failure of sparc Ubuntu trunk. Full details are available at: http://www.python.org/dev/buildbot/all/sparc%20Ubuntu%20trunk/builds/452 Buildbot URL: http://www.python.org/dev/buildbot/all/ Buildslave for this Build: klose-ubuntu-sparc Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: jeffrey.yasskin,trent.nelson BUILD FAILED: failed test Excerpt from the test logfile: 1 test failed: test_socket ====================================================================== FAIL: testAddressReuseSemantics (test.test_socket.GeneralModuleTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/pybot/buildarea/trunk.klose-ubuntu-sparc/build/Lib/test/test_socket.py", line 552, in testAddressReuseSemantics self.fail("expected EADDRINUSE socket.error exception to be " \ AssertionError: expected EADDRINUSE socket.error exception to be raised when attempting to bind a second socket to a (host, port) we've already bound to (SO_REUSEADDR *WAS* set on the socket) make: *** [buildbottest] Error 1 sincerely, -The Buildbot

1 0

r62156 - python/trunk/Lib/test/test_socket.py
by trent.nelson 04 Apr '08

04 Apr '08

Author: trent.nelson Date: Fri Apr 4 22:04:09 2008 New Revision: 62156 Modified: python/trunk/Lib/test/test_socket.py Log: Revert r62152 (Issue #2550). Being able to observe the results of all the buildbots was certainly useful. All of the platforms that have some form of BSD lineage -- FreeBSD, OS X, Solaris and Tru64 -- all pass the test. Windows and Linux, on the other hand, don't. Windows I knew about, Linux was a surprise. Knowing this, I believe a more appropriate fix will revolve around test_support.bind_socket() -- this method needs to return a port that nothing in the system has bound already. The best way to do this may just be to rely on ephemeral ports, rather than having the user specify a desired port, then fall back to four random ports, then try 0. Modified: python/trunk/Lib/test/test_socket.py ============================================================================== --- python/trunk/Lib/test/test_socket.py (original) +++ python/trunk/Lib/test/test_socket.py Fri Apr 4 22:04:09 2008 @@ -3,7 +3,6 @@ import unittest from test import test_support -import errno import socket import select import thread, threading @@ -487,81 +486,6 @@ reuse = sock.getsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR) self.failIf(reuse == 0, "failed to set reuse mode") - def testAddressReuseSemantics(self): - # As per the 'SO_REUSEADDR and SO_REUSEPORT Socket Options' section in - # chapter 7.5 of Stevens' UNIX Network Programming Volume 1 (2nd Ed): - # - # "With TCP, we are never able to start multiple servers that bind - # the same IP address and same port: a completely duplicate binding. - # That is, we cannot start one server that binds 198.69.10.2 port 80 - # and start another that also binds 198.69.10.2 port 80, even if we - # set the SO_REUSEADDR socket option for the second server." - # - # However, on Windows, it seems that if SO_REUSEADDR is set on the 2nd - # socket, binding to an already bound (host, port) combination doesn't - # raise an exception. Instead, it causes Python to wedge pretty badly - # when accept() is called against either of the sockets. This test case - # is being added to help debug this issue, as well as seeing if the - # expected semantics differ on any other platforms. - - # Get a port that we *know* is unique. Don't rely on test_support's - # bind_port method, as this operates under the assumption that an - # EADDRINUSE exception will be raised correctly, which is exactly what - # we're trying to test here. - host = '127.0.0.1' - sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM) - sock.bind((host, 0)) - port = sock.getsockname()[1] - sock.close() - del sock - - # First test that we get EADDRINUSE without SO_REUSEADDR. - sock1 = socket.socket(socket.AF_INET, socket.SOCK_STREAM) - sock1.bind((host, port)) - sock2 = socket.socket(socket.AF_INET, socket.SOCK_STREAM) - try: - sock2.bind((host, port)) - except socket.error, (err, msg): - self.assertEqual(err, errno.EADDRINUSE) - else: - self.fail("expected EADDRINUSE socket.error exception to be " \ - "raised when attempting to bind a second socket to " \ - "a (host, port) we've already bound to (SO_REUSEADDR " \ - "was NOT set on the socket)") - finally: - sock1.close() - try: - sock2.close() - except: - pass - del sock1 - del sock2 - - # Try again with SO_REUSEADDR; the behaviour *should* be identical to - # the test above, i.e. an EADDRINUSE socket.error should be raised. - sock1 = socket.socket(socket.AF_INET, socket.SOCK_STREAM) - sock1.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) - sock1.bind((host, port)) - sock2 = socket.socket(socket.AF_INET, socket.SOCK_STREAM) - sock2.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) - try: - sock2.bind((host, port)) - except socket.error, (err, msg): - self.assertEqual(err, errno.EADDRINUSE) - else: - self.fail("expected EADDRINUSE socket.error exception to be " \ - "raised when attempting to bind a second socket to " \ - "a (host, port) we've already bound to (SO_REUSEADDR " \ - "*WAS* set on the socket)") - finally: - sock1.close() - try: - sock2.close() - except: - pass - del sock1 - del sock2 - def testSendAfterClose(self): # testing send() after close() with timeout sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)

1 0

buildbot failure in x86 FreeBSD trunk
by buildbot＠python.org 04 Apr '08

04 Apr '08

The Buildbot has detected a new failure of x86 FreeBSD trunk. Full details are available at: http://www.python.org/dev/buildbot/all/x86%20FreeBSD%20trunk/builds/849 Buildbot URL: http://www.python.org/dev/buildbot/all/ Buildslave for this Build: bolen-freebsd Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: jeffrey.yasskin,trent.nelson BUILD FAILED: failed test Excerpt from the test logfile: sincerely, -The Buildbot

1 0

r62154 - python/trunk/Misc/NEWS
by thomas.heller 04 Apr '08

04 Apr '08

Author: thomas.heller Date: Fri Apr 4 21:43:25 2008 New Revision: 62154 Modified: python/trunk/Misc/NEWS Log: News entry for: Sync with files from the just released libffi 3.0.5 version. Modified: python/trunk/Misc/NEWS ============================================================================== --- python/trunk/Misc/NEWS (original) +++ python/trunk/Misc/NEWS Fri Apr 4 21:43:25 2008 @@ -18,6 +18,10 @@ Library ------- +- The bundled libffi copy is now in sync with the recently released + libffi3.0.5 version, apart from some small changes to + Modules/_ctypes/libffi/configure.ac. + - Issue #2385: distutils.core.run_script() makes __file__ available, so the controlled environment will more closely mirror the typical script environment. This supports setup.py scripts that refer to data files.

1 0

buildbot failure in x86 XP-4 trunk
by buildbot＠python.org 04 Apr '08

04 Apr '08

The Buildbot has detected a new failure of x86 XP-4 trunk. Full details are available at: http://www.python.org/dev/buildbot/all/x86%20XP-4%20trunk/builds/934 Buildbot URL: http://www.python.org/dev/buildbot/all/ Buildslave for this Build: bolen-windows Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: jeffrey.yasskin,thomas.heller,trent.nelson BUILD FAILED: failed test Excerpt from the test logfile: 1 test failed: test_socket ====================================================================== FAIL: testAddressReuseSemantics (test.test_socket.GeneralModuleTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "E:\cygwin\home\db3l\buildarea\trunk.bolen-windows\build\lib\test\test_socket.py", line 552, in testAddressReuseSemantics self.fail("expected EADDRINUSE socket.error exception to be " \ AssertionError: expected EADDRINUSE socket.error exception to be raised when attempting to bind a second socket to a (host, port) we've already bound to (SO_REUSEADDR *WAS* set on the socket) sincerely, -The Buildbot

1 0

buildbot failure in S-390 Debian trunk
by buildbot＠python.org 04 Apr '08

04 Apr '08

The Buildbot has detected a new failure of S-390 Debian trunk. Full details are available at: http://www.python.org/dev/buildbot/all/S-390%20Debian%20trunk/builds/325 Buildbot URL: http://www.python.org/dev/buildbot/all/ Buildslave for this Build: klose-debian-s390 Build Reason: Build Source Stamp: [branch trunk] HEAD Blamelist: trent.nelson BUILD FAILED: failed test Excerpt from the test logfile: 1 test failed: test_socket ====================================================================== FAIL: testAddressReuseSemantics (test.test_socket.GeneralModuleTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/pybot/buildarea/trunk.klose-debian-s390/build/Lib/test/test_socket.py", line 552, in testAddressReuseSemantics self.fail("expected EADDRINUSE socket.error exception to be " \ AssertionError: expected EADDRINUSE socket.error exception to be raised when attempting to bind a second socket to a (host, port) we've already bound to (SO_REUSEADDR *WAS* set on the socket) make: *** [buildbottest] Error 1 sincerely, -The Buildbot

1 0

r62153 - python/trunk/Modules/_ctypes/libffi/README python/trunk/Modules/_ctypes/libffi/configure python/trunk/Modules/_ctypes/libffi/configure.ac python/trunk/Modules/_ctypes/libffi/libffi.pc.in
by thomas.heller 04 Apr '08

04 Apr '08

Author: thomas.heller Date: Fri Apr 4 21:14:42 2008 New Revision: 62153 Removed: python/trunk/Modules/_ctypes/libffi/libffi.pc.in Modified: python/trunk/Modules/_ctypes/libffi/README python/trunk/Modules/_ctypes/libffi/configure python/trunk/Modules/_ctypes/libffi/configure.ac Log: More files from libffi 3.0.5. Removed libffi.pc.in because it is not needed for ctypes. Modified: python/trunk/Modules/_ctypes/libffi/README ============================================================================== --- python/trunk/Modules/_ctypes/libffi/README (original) +++ python/trunk/Modules/_ctypes/libffi/README Fri Apr 4 21:14:42 2008 @@ -1,7 +1,7 @@ Status ====== -libffi-3.0.4 was released on February 24, 2008. Check the libffi web +libffi-3.0.5 was released on April 3, 2008. Check the libffi web page for updates: <URL:http://sourceware.org/libffi/>. @@ -158,6 +158,11 @@ History ======= +3.0.5 Apr-3-08 + Fix libffi.pc file. + Fix #define ARM for IcedTea users. + Fix x86 closure bug. + 3.0.4 Feb-24-08 Fix x86 OpenBSD configury. Modified: python/trunk/Modules/_ctypes/libffi/configure ============================================================================== --- python/trunk/Modules/_ctypes/libffi/configure (original) +++ python/trunk/Modules/_ctypes/libffi/configure Fri Apr 4 21:14:42 2008 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.61 for libffi 3.0.4. +# Generated by GNU Autoconf 2.61 for libffi 3.0.5. # # Report bugs to <http://gcc.gnu.org/bugs.html>. # @@ -728,8 +728,8 @@ # Identity of this package. PACKAGE_NAME='libffi' PACKAGE_TARNAME='libffi' -PACKAGE_VERSION='3.0.4' -PACKAGE_STRING='libffi 3.0.4' +PACKAGE_VERSION='3.0.5' +PACKAGE_STRING='libffi 3.0.5' PACKAGE_BUGREPORT='http://gcc.gnu.org/bugs.html' # Factoring default headers for most tests. @@ -1459,7 +1459,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures libffi 3.0.4 to adapt to many kinds of systems. +\`configure' configures libffi 3.0.5 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1530,7 +1530,7 @@ if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of libffi 3.0.4:";; + short | recursive ) echo "Configuration of libffi 3.0.5:";; esac cat <<\_ACEOF @@ -1640,7 +1640,7 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -libffi configure 3.0.4 +libffi configure 3.0.5 generated by GNU Autoconf 2.61 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, @@ -1654,7 +1654,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by libffi $as_me 3.0.4, which was +It was created by libffi $as_me 3.0.5, which was generated by GNU Autoconf 2.61. Invocation command line was $ $0 $@ @@ -2477,7 +2477,7 @@ # Define the identity of the package. PACKAGE='libffi' - VERSION='3.0.4' + VERSION='3.0.5' cat >>confdefs.h <<_ACEOF @@ -23327,7 +23327,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by libffi $as_me 3.0.4, which was +This file was extended by libffi $as_me 3.0.5, which was generated by GNU Autoconf 2.61. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -23384,7 +23384,7 @@ _ACEOF cat >>$CONFIG_STATUS <<_ACEOF ac_cs_version="\\ -libffi config.status 3.0.4 +libffi config.status 3.0.5 configured by $0, generated by GNU Autoconf 2.61, with options \\"`echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\" Modified: python/trunk/Modules/_ctypes/libffi/configure.ac ============================================================================== --- python/trunk/Modules/_ctypes/libffi/configure.ac (original) +++ python/trunk/Modules/_ctypes/libffi/configure.ac Fri Apr 4 21:14:42 2008 @@ -1,8 +1,11 @@ dnl Process this with autoconf to create configure +# +# file from libffi - slightly patched for ctypes +# AC_PREREQ(2.59) -AC_INIT([libffi], [3.0.4], [http://gcc.gnu.org/bugs.html]) +AC_INIT([libffi], [3.0.5], [http://gcc.gnu.org/bugs.html]) AC_CONFIG_HEADERS([fficonfig.h]) AC_CANONICAL_SYSTEM Deleted: /python/trunk/Modules/_ctypes/libffi/libffi.pc.in ============================================================================== --- /python/trunk/Modules/_ctypes/libffi/libffi.pc.in Fri Apr 4 21:14:42 2008 +++ (empty file) @@ -1,10 +0,0 @@ -prefix=@prefix@ -exec_prefix=@exec_prefix@ -libdir=@libdir@ -includedir=${libdir}/@PACKAGE_NAME@-@PACKAGE_VERSION@/include - -Name: @PACKAGE_NAME@ -Description: Library supporting Foreign Function Interfaces -Version: @PACKAGE_VERSION@ -Libs: -lffi -Cflags: -I${includedir}

1 0