From owner-freebsd-perl@FreeBSD.ORG Thu Jan 22 06:37:21 2015 Return-Path: Delivered-To: perl@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BCD12C6 for ; Thu, 22 Jan 2015 06:37:21 +0000 (UTC) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.227]) by mx1.freebsd.org (Postfix) with ESMTP id 6AF3AF7B for ; Thu, 22 Jan 2015 06:37:20 +0000 (UTC) Received: from [204.210.114.114] ([204.210.114.114:24846] helo=localhost.hawaii.res.rr.com) by dnvrco-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 1A/EB-07077-FD990C45; Thu, 22 Jan 2015 06:34:07 +0000 Received: by localhost.hawaii.res.rr.com (Postfix, from userid 1000) id 3E3245CF1; Wed, 21 Jan 2015 20:38:53 -1000 (HST) Date: Wed, 21 Jan 2015 20:38:53 -1000 From: parv To: perl@freebsd.org Subject: perl 5.21.7 - test fail of cpan/IO-Socket-IP/t/01local-client-v4.t Message-ID: <20150122063853.GA3463@holstein.holy.cow> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-RR-Connecting-IP: 107.14.64.130:25 X-Authority-Analysis: v=2.1 cv=RO89HuS+ c=1 sm=1 tr=0 a=lLOF/jpPrR0dcgWXP1EvZg==:117 a=lLOF/jpPrR0dcgWXP1EvZg==:17 a=ayC55rCoAAAA:8 a=kj9zAlcOel0A:10 a=Ymsr-CWnAAAA:8 a=YNv0rlydsVwA:10 a=zpD5Ov42bEgyDjIoNzUA:9 a=CjuIK1q_8ugA:10 X-Cloudmark-Score: 0 X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 06:37:21 -0000 Has anybody noticed the test failure (in perl 5.21.7) related to socket address in cpan/IO-Socket-IP/t/01local-client-v4.t when multiple aliases exist for 127.0.0.1 ... # cd ~/tmp/perl/perl-5.21.7 # export LD_LIBRARY_PATH=`pwd`; perl cpan/IO-Socket-IP/t/01local-client-v4.t ... ok 9 - $socket->peerport for SOCK_STREAM not ok 10 - $socket->sockaddr for SOCK_STREAM # Failed test '$socket->sockaddr for SOCK_STREAM' # at cpan/IO-Socket-IP/t/01local-client-v4.t line 66. # got: '7f000002' # expected: '7f000001' ok 11 - $socket->peeraddr for SOCK_STREAM ok 12 - $socket not connected after close for SOCK_STREAM ... ok 21 - $socket->peerport for SOCK_DGRAM not ok 22 - $socket->sockaddr for SOCK_DGRAM # Failed test '$socket->sockaddr for SOCK_DGRAM' # at cpan/IO-Socket-IP/t/01local-client-v4.t line 66. # got: '7f000002' # expected: '7f000001' ok 23 - $socket->peeraddr for SOCK_DGRAM ... ... ? The related lines are ... # Some odd locations like BSD jails might not like INADDR_LOOPBACK. We'll # establish a baseline first to test against my $INADDR_LOOPBACK = do { socket my $sockh, PF_INET, SOCK_STREAM, 0 or die "Cannot socket(PF_INET) - $!"; bind $sockh, pack_sockaddr_in( 0, inet_aton( "127.0.0.1" ) ) or die "Cannot bind() - $!"; ( unpack_sockaddr_in( getsockname $sockh ) )[1]; }; my $INADDR_LOOPBACK_HOST = inet_ntoa( $INADDR_LOOPBACK ); if( $INADDR_LOOPBACK ne INADDR_LOOPBACK ) { diag( "Testing with INADDR_LOOPBACK=$INADDR_LOOPBACK_HOST; this may be because of odd networking" ); } my $INADDR_LOOPBACK_HEX = unpack "H*", $INADDR_LOOPBACK; . . . is( unpack("H*", $socket->sockaddr), $INADDR_LOOPBACK_HEX, \ "\$socket->sockaddr for $socktype" ); As I do have these ... # ifconfig lo0 lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0xd inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 inet 127.0.0.2 netmask 0xffffff00 inet 127.0.0.3 netmask 0xffffff00 inet 127.0.0.4 netmask 0xffffff00 nd6 options=3 ... should test failures be expected, and are not a problem? - parv --