Mercurial > hg
view tests/test-debugbackupbundle.t @ 46015:f44b9c72f061
run-tests: allow some slack about 'waiting on lock' message
It is common to run the tests on very loaded machine when concurrent run might
take a bit longer. Such message are usually harmless, but anoying as they break
the tests.
Test that explicitly depends on this value have been adjusted. This make them
more robust anyway.
A fun case was `test-clone-pull-corruption.t` which, without the previous
changeset introducing extra flushing, ended use having a line 31 (`pulling from
../source`) changing order because the warning message was no longer flushing
stdin before using stderr (stderr being invisible in the test).
Differential Revision: https://phab.mercurial-scm.org/D9507
author | Pierre-Yves David <pierre-yves.david@octobus.net> |
---|---|
date | Wed, 02 Dec 2020 20:10:27 +0100 |
parents | 20d74eebe56c |
children |
line wrap: on
line source
$ cat >> $HGRCPATH << EOF > [extensions] > strip= > EOF Setup repo $ hg init repo $ cd repo Test backups list and recover $ hg debugbackupbundle no backup changesets found $ mkcommit() { > echo "$1" > "$1" > hg add "$1" > hg ci -l $1 > } $ mkcommit a $ mkcommit b $ hg strip . 0 files updated, 0 files merged, 1 files removed, 0 files unresolved saved backup bundle to $TESTTMP/repo/.hg/strip-backup/d2ae7f538514-2953539b-backup.hg $ hg debugbackupbundle Recover changesets using: hg debugbackupbundle --recover <changeset hash> Available backup changesets: * (glob) d2ae7f538514 b $ hg debugbackupbundle --recover d2ae7f538514 Unbundling d2ae7f538514 adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files new changesets d2ae7f538514 (1 drafts)