facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-10 08:47:12 +03:00
Code Issues Projects Releases Wiki Activity
0e479f3794
sapling/tests/test-infinitepush-pullbackup.t

291 lines
9.2 KiB
Perl
Raw Normal View History

infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ . "$TESTDIR/library.sh"
$ . "$TESTDIR/library-infinitepush.sh"
$ setupcommon
infinitepush: prevent hg pullbackup from doing an automatic backup Summary: Instead of making an autobackup, make hg pullbackup simply write the backup state from the recently restored backup. Test Plan: cd ~/facebook-hg-rpms/fb-hgext/tests source ../../hg-dev rt test-infinitepush-*.t Reviewers: #mercurial, cdown, stash Reviewed By: stash Subscribers: mjpieters, medson Differential Revision: https://phabricator.intern.facebook.com/D6186148 Tasks: T22856338 Tags: bootcamp Signature: 6186148:1509457565:e66cefc6e95d9b1cfb91e9bf8fa5c40b05e4fb82
2017-10-31 17:00:31 +03:00
$ cat >> $HGRCPATH << EOF
> [infinitepushbackup]
> logdir=$TESTTMP/logs
> EOF
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
Setup server
$ hg init repo
$ cd repo
$ setupserver
$ cd ..
Create backup source
$ hg clone ssh://user@dummy/repo backupsource -q
Create restore target
$ hg clone ssh://user@dummy/repo restored -q
Backup
$ cd backupsource
$ mkcommit firstcommit
$ hg book abook
infinitepush: run backup check before backup from time to time Summary: It's a good way to check if backup is consistent. If backup is not consistent then we set special exit code that will be logged. It let's us easily find users with inconsistent backups and fix it. Test Plan: arc unit Reviewers: #mercurial Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4810442 Tasks: 15389402
2017-04-05 10:56:28 +03:00
Actually do a backup, make sure that backup check doesn't fail for empty backup state
infinitepush: remove some unused options Summary: Infinitepush has too many options and many of them are unused or has never been changed from the default value. Let's remove some of them. Test Plan: Run infinitepush tests Reviewers: #fbhgext, ryanmce Reviewed By: #fbhgext, ryanmce Subscribers: ryanmce Differential Revision: https://phab.mercurial-scm.org/D141
2017-07-20 11:20:59 +03:00
$ hg pushbackup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
searching for changes
remote: pushing 1 commit:
remote: 89ecc969c0ac firstcommit
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
finished in \d+\.(\d+)? seconds (re)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ cd ..
infinitepush: prevent hg pullbackup from doing an automatic backup Summary: Instead of making an autobackup, make hg pullbackup simply write the backup state from the recently restored backup. Test Plan: cd ~/facebook-hg-rpms/fb-hgext/tests source ../../hg-dev rt test-infinitepush-*.t Reviewers: #mercurial, cdown, stash Reviewed By: stash Subscribers: mjpieters, medson Differential Revision: https://phabricator.intern.facebook.com/D6186148 Tasks: T22856338 Tags: bootcamp Signature: 6186148:1509457565:e66cefc6e95d9b1cfb91e9bf8fa5c40b05e4fb82
2017-10-31 17:00:31 +03:00
Create logdir
$ setuplogdir
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
Restore
$ cd restored
infinitepush: prevent hg pullbackup from doing an automatic backup Summary: Instead of making an autobackup, make hg pullbackup simply write the backup state from the recently restored backup. Test Plan: cd ~/facebook-hg-rpms/fb-hgext/tests source ../../hg-dev rt test-infinitepush-*.t Reviewers: #mercurial, cdown, stash Reviewed By: stash Subscribers: mjpieters, medson Differential Revision: https://phabricator.intern.facebook.com/D6186148 Tasks: T22856338 Tags: bootcamp Signature: 6186148:1509457565:e66cefc6e95d9b1cfb91e9bf8fa5c40b05e4fb82
2017-10-31 17:00:31 +03:00
$ hg pullbackup --config infinitepushbackup.autobackup=True
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
pulling from ssh://user@dummy/repo
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
tests: update tests output Upstream 4a405ffd8b20 ("transaction-summary: show the range of new revisions upon pull/unbundle (BC)", 2017-10-12) has changed the output.
2017-10-17 23:05:18 +03:00
new changesets 89ecc969c0ac
infinitepush: wrap findcommonincoming if nodes are requested Summary: Previously we don't set findcommonincoming to True, and that bug was unnoticed because we send this info anyway in server-side `getbundlechunks()` function. But next diff in the stack uses a fast path server-side which won't work if fincommonincoming is not set to True. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4770830 Tasks: 15389402 Signature: t1:4770830:1490719209:c251002d992e244580b7dbfeca0c30dff95734d2
2017-03-29 13:10:12 +03:00
(run 'hg update' to get a working copy)
infinitepush: prevent hg pullbackup from doing an automatic backup Summary: Instead of making an autobackup, make hg pullbackup simply write the backup state from the recently restored backup. Test Plan: cd ~/facebook-hg-rpms/fb-hgext/tests source ../../hg-dev rt test-infinitepush-*.t Reviewers: #mercurial, cdown, stash Reviewed By: stash Subscribers: mjpieters, medson Differential Revision: https://phabricator.intern.facebook.com/D6186148 Tasks: T22856338 Tags: bootcamp Signature: 6186148:1509457565:e66cefc6e95d9b1cfb91e9bf8fa5c40b05e4fb82
2017-10-31 17:00:31 +03:00
$ waitbgbackup
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ hg log --graph -T '{desc}'
o firstcommit
$ hg book
abook 0:89ecc969c0ac
$ cd ..
infinitepush: prevent hg pullbackup from doing an automatic backup Summary: Instead of making an autobackup, make hg pullbackup simply write the backup state from the recently restored backup. Test Plan: cd ~/facebook-hg-rpms/fb-hgext/tests source ../../hg-dev rt test-infinitepush-*.t Reviewers: #mercurial, cdown, stash Reviewed By: stash Subscribers: mjpieters, medson Differential Revision: https://phabricator.intern.facebook.com/D6186148 Tasks: T22856338 Tags: bootcamp Signature: 6186148:1509457565:e66cefc6e95d9b1cfb91e9bf8fa5c40b05e4fb82
2017-10-31 17:00:31 +03:00
Check that autobackup doesn't happen on pullbackup. Logs should be empty and backupstate should be correct
$ cat $TESTTMP/logs/test/*
cat: $TESTTMP/logs/test/*: No such file or directory
[1]
$ jq -MS . restored/.hg/infinitepushbackupstate
{
"bookmarks": {
"abook": "89ecc969c0ac7d7344728f1255250df7c54a56af"
},
"heads": [
"89ecc969c0ac7d7344728f1255250df7c54a56af"
]
}
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
Create second backup source
$ hg clone ssh://user@dummy/repo backupsource2 -q
$ cd backupsource2
$ mkcommit secondcommit
$ hg book secondbook
$ hg pushbackup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
searching for changes
remote: pushing 1 commit:
remote: c1bfda8efb6e secondcommit
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
finished in \d+\.(\d+)? seconds (re)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ cd ..
Restore with ambiguous repo root
$ rm -rf restored
$ hg clone ssh://user@dummy/repo restored -q
$ cd restored
$ hg pullbackup
abort: ambiguous repo root to restore: ['$TESTTMP/backupsource', '$TESTTMP/backupsource2']
(set --reporoot to disambiguate)
[255]
$ hg pullbackup --reporoot $TESTTMP/backupsource2
pulling from ssh://user@dummy/repo
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
tests: update tests output Upstream 4a405ffd8b20 ("transaction-summary: show the range of new revisions upon pull/unbundle (BC)", 2017-10-12) has changed the output.
2017-10-17 23:05:18 +03:00
new changesets c1bfda8efb6e
infinitepush: wrap findcommonincoming if nodes are requested Summary: Previously we don't set findcommonincoming to True, and that bug was unnoticed because we send this info anyway in server-side `getbundlechunks()` function. But next diff in the stack uses a fast path server-side which won't work if fincommonincoming is not set to True. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4770830 Tasks: 15389402 Signature: t1:4770830:1490719209:c251002d992e244580b7dbfeca0c30dff95734d2
2017-03-29 13:10:12 +03:00
(run 'hg update' to get a working copy)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ hg log --graph -T '{desc}'
o secondcommit
$ cd ..
Check bookmarks escaping
$ cd backupsource
$ hg book book/bookmarks/somebook
$ hg book book/bookmarksbookmarks/somebook
$ hg pushbackup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
finished in \d+\.(\d+)? seconds (re)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ cd ../restored
$ hg pullbackup --reporoot $TESTTMP/backupsource
pulling from ssh://user@dummy/repo
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files (+1 heads)
tests: update tests output Upstream 4a405ffd8b20 ("transaction-summary: show the range of new revisions upon pull/unbundle (BC)", 2017-10-12) has changed the output.
2017-10-17 23:05:18 +03:00
new changesets 89ecc969c0ac
infinitepush: wrap findcommonincoming if nodes are requested Summary: Previously we don't set findcommonincoming to True, and that bug was unnoticed because we send this info anyway in server-side `getbundlechunks()` function. But next diff in the stack uses a fast path server-side which won't work if fincommonincoming is not set to True. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4770830 Tasks: 15389402 Signature: t1:4770830:1490719209:c251002d992e244580b7dbfeca0c30dff95734d2
2017-03-29 13:10:12 +03:00
(run 'hg heads' to see heads, 'hg merge' to merge)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ hg book
abook 1:89ecc969c0ac
book/bookmarks/somebook 1:89ecc969c0ac
book/bookmarksbookmarks/somebook 1:89ecc969c0ac
secondbook 0:c1bfda8efb6e
$ cd ..
Create a repo with `/bookmarks/` in path
$ mkdir bookmarks
$ cd bookmarks
$ hg clone ssh://user@dummy/repo backupsource3 -q
$ cd backupsource3
$ mkcommit commitinweirdrepo
$ hg book bookbackupsource3
$ hg pushbackup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
searching for changes
remote: pushing 1 commit:
remote: a2a9ae518b62 commitinweirdrepo
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
finished in \d+\.(\d+)? seconds (re)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ cd ../../restored
$ hg pullbackup --reporoot $TESTTMP/bookmarks/backupsource3
pulling from ssh://user@dummy/repo
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files (+1 heads)
tests: update tests output Upstream 4a405ffd8b20 ("transaction-summary: show the range of new revisions upon pull/unbundle (BC)", 2017-10-12) has changed the output.
2017-10-17 23:05:18 +03:00
new changesets a2a9ae518b62
infinitepush: wrap findcommonincoming if nodes are requested Summary: Previously we don't set findcommonincoming to True, and that bug was unnoticed because we send this info anyway in server-side `getbundlechunks()` function. But next diff in the stack uses a fast path server-side which won't work if fincommonincoming is not set to True. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4770830 Tasks: 15389402 Signature: t1:4770830:1490719209:c251002d992e244580b7dbfeca0c30dff95734d2
2017-03-29 13:10:12 +03:00
(run 'hg heads .' to see heads, 'hg merge' to merge)
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ hg book
abook 1:89ecc969c0ac
book/bookmarks/somebook 1:89ecc969c0ac
book/bookmarksbookmarks/somebook 1:89ecc969c0ac
bookbackupsource3 2:a2a9ae518b62
secondbook 0:c1bfda8efb6e
infinitepush: pass dest to pull function Summary: Previously dest wasn't passed to pull command. This diff fixes it. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4643461 Tasks: 15389402 Signature: t1:4643461:1488501956:4684805c618d55edcf4ee1ae13d34a87e92150e6
2017-03-06 11:50:30 +03:00
Check that correct path is used in pushbackup
$ cd ../backupsource
$ hg --config paths.default=badpath --config paths.anotherpath=ssh://user@dummy/repo pushbackup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
infinitepush: pass dest to pull function Summary: Previously dest wasn't passed to pull command. This diff fixes it. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4643461 Tasks: 15389402 Signature: t1:4643461:1488501956:4684805c618d55edcf4ee1ae13d34a87e92150e6
2017-03-06 11:50:30 +03:00
abort: repository $TESTTMP/backupsource/badpath not found!
[255]
$ hg pushbackup anotherpath --config paths.default=badpath --config paths.anotherpath=ssh://user@dummy/repo
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
infinitepush: pass dest to pull function Summary: Previously dest wasn't passed to pull command. This diff fixes it. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4643461 Tasks: 15389402 Signature: t1:4643461:1488501956:4684805c618d55edcf4ee1ae13d34a87e92150e6
2017-03-06 11:50:30 +03:00
nothing to backup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
finished in \d+\.(\d+)? seconds (re)
infinitepush: pass dest to pull function Summary: Previously dest wasn't passed to pull command. This diff fixes it. Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4643461 Tasks: 15389402 Signature: t1:4643461:1488501956:4684805c618d55edcf4ee1ae13d34a87e92150e6
2017-03-06 11:50:30 +03:00
$ cd ../restored
Check that correct path is used in pullbackup
$ hg pullbackup --config paths.default=badpath --config paths.anotherpath=ssh://user@dummy/repo --reporoot $TESTTMP/bookmarks/backupsource3
abort: repository $TESTTMP/restored/badpath not found!
[255]
$ hg pullbackup anotherpath --config paths.default=badpath --config paths.anotherpath=ssh://user@dummy/repo --reporoot $TESTTMP/bookmarks/backupsource3
pulling from ssh://user@dummy/repo
no changes found
adding changesets
adding manifests
adding file changes
added 0 changesets with 0 changes to 1 files
infinitepush: pullbackup command Summary: As the name suggest it will restore backup made by `hg pushbackup`. If user has only one backup for the `dest` repo then it will be restored. But user may have backed up many local repos that points to `dest` repo. These local repos may reside on different hosts or in different repo roots. It makes restore ambiguous; `--reporoot` and `--hostname` options are used to disambiguate. Example situation: 1) User has only one laptop with mercurial repo `repo` that was cloned from remote server. He or she run `hg pushbackup`. Then laptop breaks and user gets a new one, clones the `repo` again and runs `hg restore`. It automatically restores the backup. 2) User has devserver and laptop and backups were made from both. Then if user decides to switch devserver and run `hg restore` on the new devserver he or she has to specify `--hostname`. Future plans: 1) Add `--user` option to make it possible to restore another user's backup Test Plan: Run `test-infinitepush-*` Reviewers: rmcelroy, mitrandir, durham Reviewed By: durham Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4280832 Tasks: 12479677 Signature: t1:4280832:1481565335:2a21ceafa2ff80242076a79693046514434afb40
2016-12-16 19:29:08 +03:00
$ cd ..
infinitepush: reuse bundlerepo Summary: This diff is part of the series to avoid downloading the same bundle a few times. Finally reuse the same bundlerepo. Test Plan: arc unit Reviewers: #mercurial Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4612094 Tasks: 15389402
2017-03-06 11:40:49 +03:00
Backup and restore two commits
$ cd backupsource
$ mkcommit firstinbatch
$ hg up 0
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
(leaving bookmark book/bookmarksbookmarks/somebook)
$ mkcommit secondinbatch
created new head
$ hg pushbackup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
infinitepush: reuse bundlerepo Summary: This diff is part of the series to avoid downloading the same bundle a few times. Finally reuse the same bundlerepo. Test Plan: arc unit Reviewers: #mercurial Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4612094 Tasks: 15389402
2017-03-06 11:40:49 +03:00
searching for changes
remote: pushing 3 commits:
remote: 89ecc969c0ac firstcommit
remote: 33c1c9df81e9 firstinbatch
remote: 0e1a088ff282 secondinbatch
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
finished in \d+\.(\d+)? seconds (re)
infinitepush: reuse bundlerepo Summary: This diff is part of the series to avoid downloading the same bundle a few times. Finally reuse the same bundlerepo. Test Plan: arc unit Reviewers: #mercurial Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4612094 Tasks: 15389402
2017-03-06 11:40:49 +03:00
$ cd ../restored
Install server-side extension that will print message every time when bundlerepo
is created
$ cd ../repo
$ printf "\n[extensions]\nbundlerepologger=$TESTDIR/bundlerepologger.py" >> .hg/hgrc
$ hg st
$ cd ../restored
Pull the backup and check bundlerepo was created only once
$ hg pullbackup --reporoot $TESTTMP/backupsource | grep 'creating bundlerepo'
remote: creating bundlerepo
infinitepush: add user cmd-line option Summary: Option to specify whose backup to restore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4650320 Tasks: 15389402
2017-03-06 11:44:18 +03:00
$ cd ../repo
$ printf "\n[extensions]\nbundlerepologger=!" >> .hg/hgrc
$ cd ../restored
infinitepush: reuse bundlerepo Summary: This diff is part of the series to avoid downloading the same bundle a few times. Finally reuse the same bundlerepo. Test Plan: arc unit Reviewers: #mercurial Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4612094 Tasks: 15389402
2017-03-06 11:40:49 +03:00
Make sure that commits were restored
$ hg log -r '33c1c9df81e9 + 0e1a088ff282' > /dev/null
infinitepush: add user cmd-line option Summary: Option to specify whose backup to restore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4650320 Tasks: 15389402
2017-03-06 11:44:18 +03:00
Backup as another user, then restore it
$ cd ../backupsource
$ mkcommit backupasanotheruser
$ hg log -r . -T '{node}\n'
e0230a60975b38a9014f098fb973199efd25c46f
$ HGUSER=anotheruser hg pushbackup
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
starting backup .* (re)
infinitepush: add user cmd-line option Summary: Option to specify whose backup to restore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4650320 Tasks: 15389402
2017-03-06 11:44:18 +03:00
searching for changes
remote: pushing 3 commits:
remote: 89ecc969c0ac firstcommit
remote: 0e1a088ff282 secondinbatch
remote: e0230a60975b backupasanotheruser
infinitepush: add timestamp to the logs Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700897 Tasks: 16474976 Signature: t1:4700897:1489550188:1c6346ff158cec32df92934b585fc9cb983397c6
2017-03-16 12:20:02 +03:00
finished in \d+\.(\d+)? seconds (re)
infinitepush: add user cmd-line option Summary: Option to specify whose backup to restore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4650320 Tasks: 15389402
2017-03-06 11:44:18 +03:00
$ cd ../restored
Make sure commit was pulled by checking that commit is present
$ hg log -r e0230a60975b38a9014f098fb973199efd25c46f -T '{node}\n'
abort: unknown revision 'e0230a60975b38a9014f098fb973199efd25c46f'!
[255]
$ hg pullbackup --user anotheruser --reporoot $TESTTMP/backupsource > /dev/null
$ hg log -r tip -T '{node}\n'
e0230a60975b38a9014f098fb973199efd25c46f
infinitepush: add debugcheckbackup Summary: Command that checks that every head and bookmark node is present in the bundlestore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4658436 Tasks: 15389402
2017-03-07 12:21:44 +03:00
Test debugcheckbackup
infinitepush: add --all option to debugcheckbackup Summary: By default debugcheckbackup checks only one backup for the user. With --all option it checks all backups for the user from all host/reporoots Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700993 Tasks: 15389402 Signature: t1:4700993:1489548921:800d08f420acc8ef4f807ffd17b31837dbb3fe82
2017-03-16 12:22:39 +03:00
$ hg debugcheckbackup
abort: ambiguous repo root to restore: ['$TESTTMP', '$TESTTMP/backupsource', '$TESTTMP/backupsource2', '$TESTTMP/bookmarks/backupsource3']
(set --reporoot to disambiguate)
[255]
infinitepush: add debugcheckbackup Summary: Command that checks that every head and bookmark node is present in the bundlestore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4658436 Tasks: 15389402
2017-03-07 12:21:44 +03:00
$ hg debugcheckbackup --user anotheruser --reporoot $TESTTMP/backupsource
infinitepush: add --all option to debugcheckbackup Summary: By default debugcheckbackup checks only one backup for the user. With --all option it checks all backups for the user from all host/reporoots Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700993 Tasks: 15389402 Signature: t1:4700993:1489548921:800d08f420acc8ef4f807ffd17b31837dbb3fe82
2017-03-16 12:22:39 +03:00
checking \$TESTTMP/backupsource on .* (re)
infinitepush: update test to reflect upstream change It seems `debugcheckbackup` could get a new kind of error with the latest upstream code: Traceback (most recent call last): File "hg/mercurial/scmutil.py", line 150, in callcatch return func() File "hg/mercurial/dispatch.py", line 292, in _runcatchfunc return _dispatch(req) File "hg/mercurial/dispatch.py", line 896, in _dispatch cmdpats, cmdoptions) File "hg/mercurial/dispatch.py", line 658, in runcommand ret = _runcommand(ui, options, cmd, d) File "hg/mercurial/dispatch.py", line 904, in _runcommand return cmdfunc() File "hg/mercurial/dispatch.py", line 893, in <lambda> d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "hg/mercurial/extensions.py", line 322, in closure return func(*(args + a), **kw) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "hg/hgext/mq.py", line 3542, in mqcommand return orig(ui, repo, *args, **kwargs) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "fb-hgext/infinitepush/backupcommands.py", line 272, in checkbackup if not _dobackupcheck(bkpstate, ui, repo, dest, **opts): File "fb-hgext/infinitepush/backupcommands.py", line 469, in _dobackupcheck for r in lookupresults: File "hg/mercurial/wireproto.py", line 137, in results next(batchable) File "hg/mercurial/wireproto.py", line 238, in lookup self._abort(error.RepoError(data)) File "hg/mercurial/sshpeer.py", line 235, in _abort raise exception RepoError: 0e1a088ff2825213eaa838a82a842bc186f10dd5 abort: 0e1a088ff2825213eaa838a82a842bc186f10dd5! The error message only contains a commit hash, which is not friendly to be printed out. Therefore make sure we have control about the error message and update the test accordingly. Differential Revision: https://phab.mercurial-scm.org/D485
2017-08-23 07:58:37 +03:00
$ hg debugcheckbackup --all 2>&1 | sort
infinitepush: add --all option to debugcheckbackup Summary: By default debugcheckbackup checks only one backup for the user. With --all option it checks all backups for the user from all host/reporoots Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700993 Tasks: 15389402 Signature: t1:4700993:1489548921:800d08f420acc8ef4f807ffd17b31837dbb3fe82
2017-03-16 12:22:39 +03:00
checking \$TESTTMP on .* (re)
checking \$TESTTMP/backupsource on .* (re)
checking \$TESTTMP/backupsource2 on .* (re)
checking \$TESTTMP/bookmarks/backupsource3 on .* (re)
infinitepush: add debugcheckbackup Summary: Command that checks that every head and bookmark node is present in the bundlestore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4658436 Tasks: 15389402
2017-03-07 12:21:44 +03:00
$ rm ../repo/.hg/scratchbranches/index/nodemap/e0230a60975b38a9014f098fb973199efd25c46f
$ hg debugcheckbackup --user anotheruser --reporoot $TESTTMP/backupsource
infinitepush: add --all option to debugcheckbackup Summary: By default debugcheckbackup checks only one backup for the user. With --all option it checks all backups for the user from all host/reporoots Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700993 Tasks: 15389402 Signature: t1:4700993:1489548921:800d08f420acc8ef4f807ffd17b31837dbb3fe82
2017-03-16 12:22:39 +03:00
checking \$TESTTMP/backupsource on .* (re)
unknown revision 'e0230a60975b38a9014f098fb973199efd25c46f'
infinitepush: add debugcheckbackup Summary: Command that checks that every head and bookmark node is present in the bundlestore Test Plan: arc unit Reviewers: #mercurial Subscribers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4658436 Tasks: 15389402
2017-03-07 12:21:44 +03:00
[255]
infinitepush: add --all option to debugcheckbackup Summary: By default debugcheckbackup checks only one backup for the user. With --all option it checks all backups for the user from all host/reporoots Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700993 Tasks: 15389402 Signature: t1:4700993:1489548921:800d08f420acc8ef4f807ffd17b31837dbb3fe82
2017-03-16 12:22:39 +03:00
Make another backup from backupsource2 and run `hg debugcheckbackup --all` again.
Make sure that both repos were checked even though check for one of them fails
$ cd ../backupsource2
$ mkcommit newcommit
$ HGUSER=anotheruser hg pushbackup
starting backup .* (re)
searching for changes
remote: pushing 2 commits:
remote: c1bfda8efb6e secondcommit
remote: c03baa769a20 newcommit
finished in \d+\.(\d+)? seconds (re)
$ cd ../backupsource
infinitepush: update test to reflect upstream change It seems `debugcheckbackup` could get a new kind of error with the latest upstream code: Traceback (most recent call last): File "hg/mercurial/scmutil.py", line 150, in callcatch return func() File "hg/mercurial/dispatch.py", line 292, in _runcatchfunc return _dispatch(req) File "hg/mercurial/dispatch.py", line 896, in _dispatch cmdpats, cmdoptions) File "hg/mercurial/dispatch.py", line 658, in runcommand ret = _runcommand(ui, options, cmd, d) File "hg/mercurial/dispatch.py", line 904, in _runcommand return cmdfunc() File "hg/mercurial/dispatch.py", line 893, in <lambda> d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "hg/mercurial/extensions.py", line 322, in closure return func(*(args + a), **kw) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "hg/hgext/mq.py", line 3542, in mqcommand return orig(ui, repo, *args, **kwargs) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "fb-hgext/infinitepush/backupcommands.py", line 272, in checkbackup if not _dobackupcheck(bkpstate, ui, repo, dest, **opts): File "fb-hgext/infinitepush/backupcommands.py", line 469, in _dobackupcheck for r in lookupresults: File "hg/mercurial/wireproto.py", line 137, in results next(batchable) File "hg/mercurial/wireproto.py", line 238, in lookup self._abort(error.RepoError(data)) File "hg/mercurial/sshpeer.py", line 235, in _abort raise exception RepoError: 0e1a088ff2825213eaa838a82a842bc186f10dd5 abort: 0e1a088ff2825213eaa838a82a842bc186f10dd5! The error message only contains a commit hash, which is not friendly to be printed out. Therefore make sure we have control about the error message and update the test accordingly. Differential Revision: https://phab.mercurial-scm.org/D485
2017-08-23 07:58:37 +03:00
$ hg debugcheckbackup --user anotheruser --all 2>&1 | sort
infinitepush: add --all option to debugcheckbackup Summary: By default debugcheckbackup checks only one backup for the user. With --all option it checks all backups for the user from all host/reporoots Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4700993 Tasks: 15389402 Signature: t1:4700993:1489548921:800d08f420acc8ef4f807ffd17b31837dbb3fe82
2017-03-16 12:22:39 +03:00
checking \$TESTTMP/backupsource on .* (re)
checking \$TESTTMP/backupsource2 on .* (re)
infinitepush: update test to reflect upstream change It seems `debugcheckbackup` could get a new kind of error with the latest upstream code: Traceback (most recent call last): File "hg/mercurial/scmutil.py", line 150, in callcatch return func() File "hg/mercurial/dispatch.py", line 292, in _runcatchfunc return _dispatch(req) File "hg/mercurial/dispatch.py", line 896, in _dispatch cmdpats, cmdoptions) File "hg/mercurial/dispatch.py", line 658, in runcommand ret = _runcommand(ui, options, cmd, d) File "hg/mercurial/dispatch.py", line 904, in _runcommand return cmdfunc() File "hg/mercurial/dispatch.py", line 893, in <lambda> d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "hg/mercurial/extensions.py", line 322, in closure return func(*(args + a), **kw) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "hg/hgext/mq.py", line 3542, in mqcommand return orig(ui, repo, *args, **kwargs) File "hg/mercurial/util.py", line 1118, in check return func(*args, **kwargs) File "fb-hgext/infinitepush/backupcommands.py", line 272, in checkbackup if not _dobackupcheck(bkpstate, ui, repo, dest, **opts): File "fb-hgext/infinitepush/backupcommands.py", line 469, in _dobackupcheck for r in lookupresults: File "hg/mercurial/wireproto.py", line 137, in results next(batchable) File "hg/mercurial/wireproto.py", line 238, in lookup self._abort(error.RepoError(data)) File "hg/mercurial/sshpeer.py", line 235, in _abort raise exception RepoError: 0e1a088ff2825213eaa838a82a842bc186f10dd5 abort: 0e1a088ff2825213eaa838a82a842bc186f10dd5! The error message only contains a commit hash, which is not friendly to be printed out. Therefore make sure we have control about the error message and update the test accordingly. Differential Revision: https://phab.mercurial-scm.org/D485
2017-08-23 07:58:37 +03:00
unknown revision 'e0230a60975b38a9014f098fb973199efd25c46f'
infinitepush: add getavailablebackups command Summary: Command to list available backups for the user. --json will be used by automation Test Plan: arc unit Reviewers: #mercurial, simonfar Reviewed By: simonfar Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4728729 Tasks: 15389402 Signature: t1:4728729:1490005762:41b9683cb7dfc9d84ae1032c807d1f0c3fe60dbf
2017-03-29 13:00:46 +03:00
Test getavailablebackups command
$ hg getavailablebackups
user test has 4 available backups:
\$TESTTMP on .* (re)
\$TESTTMP/backupsource on .* (re)
\$TESTTMP/backupsource2 on .* (re)
\$TESTTMP/bookmarks/backupsource3 on .* (re)
$ hg getavailablebackups --user anotheruser
user anotheruser has 2 available backups:
\$TESTTMP/backupsource on .* (re)
\$TESTTMP/backupsource2 on .* (re)
$ hg getavailablebackups --json
{".*": \["\$TESTTMP", "\$TESTTMP/backupsource", "\$TESTTMP/backupsource2", "\$TESTTMP/bookmarks/backupsource3"\]} (re)
Reference in New Issue Copy Permalink