From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 05:44:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7E632A8 for ; Sun, 8 Mar 2015 05:44:41 +0000 (UTC) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9289DDA8 for ; Sun, 8 Mar 2015 05:44:40 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t285iWLw024795; Sun, 8 Mar 2015 05:44:32 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.102] (gateway.kientzle.com [192.168.1.65]) by kientzle.com with SMTP id ud4ef8yfi3vptumwaudtaiei4a; Sun, 08 Mar 2015 05:44:32 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: svn server problems From: Tim Kientzle In-Reply-To: <20150307155310.55d0e19b@ivory.wynn.com> Date: Sat, 7 Mar 2015 21:44:32 -0800 Content-Transfer-Encoding: 7bit Message-Id: References: <20150307155310.55d0e19b@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 05:44:41 -0000 > On Mar 7, 2015, at 12:53 PM, Brett Wynkoop wrote: > > Greeting- > > So I have been trying since last night to svn up my source tree on the > BBone with no luck. It seems to never complete and instead produces > the following error: > > A sys/gnu/dts/arm/zynq-zc702.dts > A sys/gnu/dts/arm/imx31-bug.dts > A sys/gnu/dts/arm/ste-href-ab8500.dtsi > svn: E120108: Error retrieving REPORT: The server unexpectedly closed > the connection. > > Is anyone else seeing this issue? Back when I did regular native build worlds, I saw this quite regularly. I was always able to eventually complete an update, but it sometimes took many many iterations of: svnlite cleanup && svnlite up before it could complete. I suspect this is an artifact of SD performance: SVN tries to keep a network connection open while its updating files locally and this leads to server timeouts. I had better luck using git. I think its update strategy does not require keeping a network connection open for such long periods of time. Tim