Date: Tue, 27 Aug 2019 02:09:29 +0200 From: Per Hedeland <per@hedeland.org> To: Russell Haley <russ.haley@gmail.com>, Ronald Klop <ronald-lists@klop.ws> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: svn timeout - Re: Espressobin anyone ? Message-ID: <4168768c-3c9d-f813-97b8-fe0d0538fef2@hedeland.org> In-Reply-To: <CABx9NuTWYM4j1wwLEEqcyftyV=bRaPSm4a9GjiwV4OfneXqQSg@mail.gmail.com> References: <E73AFF5D-43CA-41A7-BDBA-ADEF2D342479@deepcore.dk> <CAAkMUSXd2zQQcYWDZnmibTQzLe%2BUV8rH6pk5fr=oZvevAY%2BHOQ@mail.gmail.com> <6DA8E736-8031-4BF7-8B20-CF8B0E8A7FEF@gmail.com> <CAAkMUSVRxbDBYtX0g7xbu4kLtiYQiZhjh0bdSwbCahF%2BjmTUXg@mail.gmail.com> <CAAkMUSVWWjYviHbOUXuHPxJYoahUnitdNazyusH=zGvbW1RAnw@mail.gmail.com> <ABB6B2F0-7771-49CD-84CF-B00D061EEF60@gmail.com> <CAAkMUSUfKN8Jqe7U40z9O1ypb=WuMWfgGtbnq7jLFPjp5qQfqQ@mail.gmail.com> <CAAkMUSV4p1uQOi%2Bt7b-z0uG8kjVY3qZhFd4B7fP1BjOWVRYqTA@mail.gmail.com> <BC161A1F-DC68-4AD3-BD28-1028E4BF7CCD@gmail.com> <CAAkMUSVGZCxgoTc%2BfBgsuR-DKiwUm8gKe49W-2%2BhH2PqRc%2Bg2A@mail.gmail.com> <CAAkMUSW6Oa-RE4MFMKghn3XfMN5tL0MQE=z1h5jO8H7=XS8%2BXA@mail.gmail.com> <2002575095.53.1566305166664@localhost> <CAAkMUSWv%2B0m29Epy0ZA1rnbLTJ2XkNTG2aSN7e11eGxE-3tYXw@mail.gmail.com> <op.z6t4g5ajkndu52@sjakie> <CAAkMUSUr56Dv8S6syPtf=yfUkiiykJxoVNexaVv5KHwRvJ29yg@mail.gmail.com> <op.z65emajykndu52@sjakie> <CABx9NuTWYM4j1wwLEEqcyftyV=bRaPSm4a9GjiwV4OfneXqQSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-08-26 23:58, Russell Haley wrote: > On Mon, Aug 26, 2019 at 2:15 PM Ronald Klop <ronald-lists@klop.ws> wrote: > >> On Fri, 23 Aug 2019 00:27:00 +0200, Jeffrey Bowers <khantroll@gmail.com> >> wrote: >> >>> No, unfortunately it still ends in an E000060: Operation timed out. >>> However, there are files and directories in my local ports directory, >>>> so it's downloading at least some things. >> >> >> One more option I can think of. >> svn checkout svn://svn.freebsd.org/ports/head > > > I reverted to using the svn protocol many moons ago because http wouldn't > work at all. The svn protocol still fails a few times on any given > checkout, but re-starting the checkout picks up where it left off. I always > build on a PC so it's not a slow SD card problem, it seems to be a long > standing issue retrieving source code. > > Just my observation, > Russ > >> >> >> So not svn+ssh://, but only svn://. I just noticed my RPI3 uses that for >> sources. >> >> Something else I have seen in the past is that the local disk (like a >> cheap SD-card) can be too slow and causes timeouts because SVN can't >> write >> fast enough to keep the network busy. Which might happen earlier if you >> checkout using https compared to the svn-protocol. Just another data point - I encountered this exact problem recently, while trying to checkout (base, not ports) directly onto a USB stick, using https. It was very slow, and eventually svn reported an error regarding the reception of data (unfortunately I didn't record the exact code or message). Did the checkout to a directory on a SATA disk instead, still using https - worked fine - and then tarred the tree over to the USB stick - took forever, but also worked fine. So clearly the server may lose patience if the transfer is too slow...:-) I haven't retried the checkout-directly-to-USB-stick using svn instead of https, though. --Per >> Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4168768c-3c9d-f813-97b8-fe0d0538fef2>