Take the 2-minute tour ×

I have a strange problem with updating Mercurial. Everytime when I add a file to my repository and then update another location of the repository (for example with in CI process), the error "no match found" occures. Then when I remove to whole folder and clone it again there are no problems and the new added file(s) are there. Updating and removing doesnt give problems

When I do "a" Verify the following is shown:

data/test.txt.i@54: missing revlog! 54: empty or missing test.txt test.txt@54: b80de5d13875 in manifests not found 3 integrity errors encountered! (first damaged changeset appears to be 54)

Any idea what could be causing this?


The complete trace:

ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: abort: data/test.txt.i@b80de5d13875: no match found! . Process command: hg update --noninteractive at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute(ProcessInfo processInfo) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Mercurial.Mercurial.GetSource(IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build(IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate(IntegrationRequest request)

share|improve this question
Can you post a trace showing the exact commands you're running and the output they give? –  crazyscot Jun 9 '10 at 12:54
It sounds like you somehow managed to get a corrupt repository. This more properly belongs on the mercurial mailing list or the freenode IRC channel because it looks like a bug. –  Omnifarious Jun 9 '10 at 13:00
How can I run a trace? –  Ivo Jun 9 '10 at 13:02
It's not running a trace, it's giving a list of the exact commands you run and what their output is. Basically cut & paste the terminal window in which your having the problem showing the relevant stuff. –  Omnifarious Jun 9 '10 at 13:05
I added the full error message –  Ivo Jun 9 '10 at 13:13
add comment

1 Answer

up vote 2 down vote accepted

The "repository corruption" is not patent here, since you can clone again, and retrieve the all content (old and newly added).
So the different points to check are:

1/ process conflict of some kind (something preventing data/test.txt.i@b80de5d13875 to be written, even so the file content is recorded)
2/ hg revlog and hg debugindex, to check out the versions actually recorded in your repo.
3/ hg verify to rule out any repo corruption.
4/ check the integrity of your repo

share|improve this answer
Thanks I am going to try this, will let you know the result –  Ivo Jun 10 '10 at 7:49
The issue is solved, I changed the Commit user on the repository and the project folder and now its solved –  Ivo Jun 15 '10 at 8:06
add comment

Your Answer


