Corruption on Clone

Issue #422 wontfix
Kevin Smith
created an issue

I recently upgraded to mercurial 3.0 and to hgsubversion tag 1.6.1 and I am seeing corruption in the files I have cloned.

After reading a similar issue I ran clone with the --stupid option and was flooded with Hunk Failed messages. After letting it run for a while it crashed with the following message:

"svn: In file '......\subversion\libsvn_ra\ra_loader.c' line 595: assertion failed (*path != '/')

This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."

Unfortunately it is a large internal repo and creating a smaller sample would be difficult.

Comments (6)

  1. Augie Fackler repo owner

    Is there any chance you can bisect it down to an hgsubversion commit that's causing the problem?

    Note that it's very unlikely we can help you without a sample repository.

  2. Kevin Smith reporter

    The difficulty here is I am unsure as to where to start looking for the root of the problem. I only noticed it when I attempted to apply a changeset from an older repo and had it fail due to 4k lines disappearing from the file I was attempting to merge into in the fresh clone.

  3. Kevin Smith reporter

    I actually went and re looked into where I thought the problem was occurring and found that its actually happening on the first changeset. The file in the first changeset contains about half the lines that are in the original svn commit. This explains all the hunk failed messages since the files were incomplete right from the start. Now the only question is why the files are incomplete since they are complete in the svn repo!

  4. Log in to comment