From owner-cvs-ports@FreeBSD.ORG Wed Jan 24 23:57:01 2007 Return-Path: X-Original-To: cvs-ports@freebsd.org Delivered-To: cvs-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6895816A400; Wed, 24 Jan 2007 23:57:01 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5795313C471; Wed, 24 Jan 2007 23:57:01 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 346301A4D86; Wed, 24 Jan 2007 15:57:01 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A2B2351577; Wed, 24 Jan 2007 18:56:56 -0500 (EST) Date: Wed, 24 Jan 2007 18:56:56 -0500 From: Kris Kennaway To: Mikhail Teterin Message-ID: <20070124235656.GA41072@xor.obsecurity.org> References: <200701231143.l0NBhSRF010390@repoman.freebsd.org> <200701241635.47510@aldan> <20070124214042.GA39398@xor.obsecurity.org> <200701241847.53537@aldan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701241847.53537@aldan> User-Agent: Mutt/1.4.2.2i Cc: cvs-ports@freebsd.org, ports-committers@freebsd.org, Kris Kennaway Subject: Re: tcltls hanging in self-tests? (Re: cvs commit: ports/devel/tcllib Makefile) X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 23:57:01 -0000 On Wed, Jan 24, 2007 at 06:47:53PM -0500, Mikhail Teterin wrote: > On Wednesday 24 January 2007 16:40, Kris Kennaway wrote: > = > This is the first time I hear about the problem -- there is nothing > = > unusual or unreasonable about asking the problem-reporter for the > = > stdout/stderr, is there? > = > = No, but you have to also accept that I can't oblige, as previously stated. > > Indeed: > > = > Can I see the build-log, please? Which test is hanging? > > = I don't know, I haven't had the time to debug it (the build log does > = not exist since it does not complete). > > I accept that, and shall wait until you find the time to collect the output. > > A semi-educated guess: the problem may have to do with the build-machine > dropping (rather than nacking) attempts to connect to a closed port. Is > pointyhat (mis)configured this way? I answered this earlier too...the build machines do not behave in this way (you can verify yourself, they just build in a jail with randomly assigned 127/8 address). Maybe it's another assumption about 127.0.0.1. Kris