Mercurial > hg
view tests/test-verify.out @ 9954:d6a307719ccb stable
fix bug in prepush logic involving merge changesets
When creating new branches and merging them into existing ones, you would
sometimes be able to push some changesets (the existing branches) without using
--force, even when that creates a new head on the remote.
A test which triggers the error has been added.
author | Sune Foldager <cryo@cyanite.org> |
---|---|
date | Mon, 30 Nov 2009 14:58:52 +0100 |
parents | b33d70849a20 |
children | 581066a319e5 |
line wrap: on
line source
% prepare repo adding FOO.txt adding QUICK.txt adding bar.txt % verify checking changesets checking manifests crosschecking files in changesets and manifests checking files 3 files, 1 changesets, 3 total revisions % verify with journal abandoned transaction found - run hg recover checking changesets checking manifests crosschecking files in changesets and manifests checking files 3 files, 1 changesets, 3 total revisions % introduce some bugs in repo % verify checking changesets checking manifests crosschecking files in changesets and manifests checking files data/FOO.txt.i@0: missing revlog! 0: empty or missing FOO.txt FOO.txt@0: f62022d3d590 in manifests not found data/QUICK.txt.i@0: missing revlog! 0: empty or missing QUICK.txt QUICK.txt@0: 88b857db8eba in manifests not found data/bar.txt.i@0: missing revlog! 0: empty or missing bar.txt bar.txt@0: 256559129457 in manifests not found 3 files, 1 changesets, 0 total revisions 9 integrity errors encountered! (first damaged changeset appears to be 0) % test revlog corruption % verify checking changesets checking manifests crosschecking files in changesets and manifests checking files a@0: broken revlog! (index data/a.i is corrupted) warning: orphan revlog 'data/a.i' 1 files, 1 changesets, 0 total revisions 1 warnings encountered! 1 integrity errors encountered! (first damaged changeset appears to be 0)