Closed
Bug 1367175
Opened 7 years ago
Closed 7 years ago
Integrity check failures with robustcheckout
Categories
(Developer Services :: Mercurial: robustcheckout, defect)
Developer Services
Mercurial: robustcheckout
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1297153
People
(Reporter: jesup, Unassigned)
Details
https://treeherder.mozilla.org/logviewer.html#?job_id=101305088&repo=try&lineNumber=1216 From https://treeherder.mozilla.org/#/jobs?repo=try&revision=63966ee31d1b804010b5c6647add95f4b1a02cab 11:43:24 INFO - RevlogError: integrity check failed on 00manifest.i:399958 11:43:24 INFO - abort: integrity check failed on 00manifest.i:399958! 11:43:24 ERROR - Return code: 255 Try push, based off an inbound rev from last friday or so.
Comment 1•7 years ago
|
||
I have no clue what caused this. We do know that TC can SIGKILL containers. So it is possible for `hg` to get forcefully terminated in the middle of an `hg clone` or `hg pull`, which will corrupt the repo and lead to errors like this. I'm slightly optimistic that bug 1297153 will fix this by detecting old locks and blowing away the repo when they are seen. (An orphaned lock is a good sign that a previous process was killed forcefully.) So marking as a dupe unless we see other evidence of this post bug 1297153.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•