On Tue, Apr 21, 2009 at 9:31 AM, Simon Large <
simon.tortoisesvn_at_googlemail.com> wrote:
>
> As it is an issue with update you should be able to test this using
> the subversion command line client. You might want to make a copy of
> the entire working copy directory, just in case the problem magically
> goes away and can't be reproduced.
>
> Does a fresh checkout work, maybe a checkout of the Newton directory?
I actually traced the issue down to the leaf directory Newton/Art
Anytime an update is performed on this directory it fails. Oddly enough it
also kills other connections to other services on the same server. If I do a
fresh checkout of the Newton/Art directory by itself this issue does not
happen. If I delete the Art directory (inside of the original working copy)
and do an update, it restores the Art directory and a few of the first
files, but fails mid-way through the restoration of the directory's
contents.
I tried this with the SVN client and it fails as well with the same
behavior. So this is definitely an API issue. I'm not sure how to go about
reporting this, though. This is quite a blocker for me and I know it would
take the SVN team a while to look at this.
The error I get from SVN is below:
D:\IT\work\redsword>svn up
svn: GET of
'/subversion/!svn/bc/539/development/trunk/projects/Newton/Art/NeutronStar.png':
could not connect to server (http://coonass)
Running 'svnadmin verify' on the server's repository shows no issues either.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1844400
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-21 16:46:15 CEST