facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-10 16:57:49 +03:00
Code Issues Projects Releases Wiki Activity
b6f11be83a
sapling/eden/scm/tests/test-commitcloud-backup-lfs.t

91 lines
2.3 KiB
Perl
Raw Normal View History

tests: enable chg for 572 tests Summary: Add `#chg-compatible` to 572 tests that seem to pass with chg enabled. This should make them run faster. Reviewed By: xavierd Differential Revision: D18870507 fbshipit-source-id: fe895e733efffc9286cd3d17c7a156c803124395
2019-12-10 02:24:31 +03:00
#chg-compatible
treemanifest: enable treemanifest by default in tests Summary: Now that all our repos are treemanifest, let's enable the extension by default in tests. Once we're certain no one needs it in production we'll also make it the default in core Mercurial. This diff includes a minor fix in treemanifest to be aware of always-enabled extensions. It won't matter until we actually add treemanifest to the list of default enabled extensions, but I caught this while testing things. Reviewed By: ikostia Differential Revision: D15030253 fbshipit-source-id: d8361f915928b6ad90665e6ed330c1df5c8d8d86
2019-05-28 13:12:27 +03:00
$ setconfig extensions.treemanifest=!
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ enable amend
infinitepush: re-enable lfs support Summary: D17 was reverted because it broke creating bundle for non-general delta repos. The reason is the following: D17 made infinitepush extension override changegroup.supportedoutgoingversion() function and discard '01' version. For non-general delta repositories it resulted in broken `hg bundle ...` command. `abort: repository does not support bundle version 01` This diff fixes it by not overriding supportedoutgoingversion(). Instead getscratchbranchpart() has its own logic of selecting changegroup version. Test Plan: Run unit-test Run `hg bundle -r . --base .^ somefile` in non-general delta repo, make sure it works fine. Reviewers: #fbhgext, durham Reviewed By: #fbhgext, durham Subscribers: durham Differential Revision: https://phab.mercurial-scm.org/D81
2017-07-20 11:14:35 +03:00
Setup common infinitepush
$ . "$TESTDIR/library.sh"
infinitepush: move library-infinitepush.sh to infinitepush/library.sh Summary: Makes more sense to have this structure after D6691821. Test Plan: Ran all the tests. Reviewers: quark, #mercurial, #sourcecontrol Reviewed By: quark Differential Revision: https://phabricator.intern.facebook.com/D6694171 Signature: 6694171:1515609818:1142419346e3458db7674b1b69036d88e82a1903
2018-01-10 21:44:15 +03:00
$ . "$TESTDIR/infinitepush/library.sh"
infinitepush: re-enable lfs support Summary: D17 was reverted because it broke creating bundle for non-general delta repos. The reason is the following: D17 made infinitepush extension override changegroup.supportedoutgoingversion() function and discard '01' version. For non-general delta repositories it resulted in broken `hg bundle ...` command. `abort: repository does not support bundle version 01` This diff fixes it by not overriding supportedoutgoingversion(). Instead getscratchbranchpart() has its own logic of selecting changegroup version. Test Plan: Run unit-test Run `hg bundle -r . --base .^ somefile` in non-general delta repo, make sure it works fine. Reviewers: #fbhgext, durham Reviewed By: #fbhgext, durham Subscribers: durham Differential Revision: https://phab.mercurial-scm.org/D81
2017-07-20 11:14:35 +03:00
$ setupcommon
Setup lfs
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ enable lfs
$ setconfig experimental.changegroup3=true
$ setconfig lfs.threshold=10B lfs.url="file:$TESTTMP/dummy-remote/"
infinitepush: re-enable lfs support Summary: D17 was reverted because it broke creating bundle for non-general delta repos. The reason is the following: D17 made infinitepush extension override changegroup.supportedoutgoingversion() function and discard '01' version. For non-general delta repositories it resulted in broken `hg bundle ...` command. `abort: repository does not support bundle version 01` This diff fixes it by not overriding supportedoutgoingversion(). Instead getscratchbranchpart() has its own logic of selecting changegroup version. Test Plan: Run unit-test Run `hg bundle -r . --base .^ somefile` in non-general delta repo, make sure it works fine. Reviewers: #fbhgext, durham Reviewed By: #fbhgext, durham Subscribers: durham Differential Revision: https://phab.mercurial-scm.org/D81
2017-07-20 11:14:35 +03:00
Setup server repo
$ hg init repo
$ cd repo
$ setupserver
$ echo 1 > 1
$ hg add 1
$ hg ci -m initial
Setup client
$ cd ..
$ hg clone ssh://user@dummy/repo client -q
$ cd client
$ echo aaaaaaaaaaa > largefile
$ hg ci -Aqm commit
$ hg debugdata largefile 0
version https://git-lfs.github.com/spec/v1
oid sha256:ab483e1d855ad0ea27a68eeea02a04c1de6ccd2dc2c05e3a48c9a1ebb8af5f99
size 12
x-is-binary 0
$ hg push -r . --to scratch/lfscommit --create
pushing to ssh://user@dummy/repo
searching for changes
remote: pushing 1 commit:
remote: 0da81a72db1a commit
$ scratchbookmarks
scratch/lfscommit 0da81a72db1a2d8256845e3808971f33e73d24c4
$ cd ..
Setup another client
$ hg clone ssh://user@dummy/repo client2 -q
$ cd client2
$ hg update scratch/lfscommit
'scratch/lfscommit' does not exist locally - looking for it remotely...
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
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 0da81a72db1a
infinitepush: re-enable lfs support Summary: D17 was reverted because it broke creating bundle for non-general delta repos. The reason is the following: D17 made infinitepush extension override changegroup.supportedoutgoingversion() function and discard '01' version. For non-general delta repositories it resulted in broken `hg bundle ...` command. `abort: repository does not support bundle version 01` This diff fixes it by not overriding supportedoutgoingversion(). Instead getscratchbranchpart() has its own logic of selecting changegroup version. Test Plan: Run unit-test Run `hg bundle -r . --base .^ somefile` in non-general delta repo, make sure it works fine. Reviewers: #fbhgext, durham Reviewed By: #fbhgext, durham Subscribers: durham Differential Revision: https://phab.mercurial-scm.org/D81
2017-07-20 11:14:35 +03:00
'scratch/lfscommit' found remotely
display inifinitepush pull time Reviewed By: StanislavGlebik Differential Revision: D6748718 fbshipit-source-id: c1b5b529d1c492017e07a67629d8908bb0d19bb4
2018-01-23 23:08:32 +03:00
pull finished in * sec (glob)
infinitepush: re-enable lfs support Summary: D17 was reverted because it broke creating bundle for non-general delta repos. The reason is the following: D17 made infinitepush extension override changegroup.supportedoutgoingversion() function and discard '01' version. For non-general delta repositories it resulted in broken `hg bundle ...` command. `abort: repository does not support bundle version 01` This diff fixes it by not overriding supportedoutgoingversion(). Instead getscratchbranchpart() has its own logic of selecting changegroup version. Test Plan: Run unit-test Run `hg bundle -r . --base .^ somefile` in non-general delta repo, make sure it works fine. Reviewers: #fbhgext, durham Reviewed By: #fbhgext, durham Subscribers: durham Differential Revision: https://phab.mercurial-scm.org/D81
2017-07-20 11:14:35 +03:00
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
(activating bookmark scratch/lfscommit)
infinitepush: fix infinitepush pull for cgversion 3 Summary: Previously if only cgversion 3 is supported by the server, then hg up HASH may fail if _rebundle() is needed. This diff fixes it by implementing the same logic as upstream mercurial. It uses bundle capabilities to find out which versions client supports and it intersects it with versions that are supported by the server. This is grafted from D6655986 Test Plan: Tested in fb-hgext: ran unit-test Reviewers: Subscribers: Tasks: Tags:
2018-01-10 09:41:46 +03:00
Make pushbackup that contains bundle with 2 heads
$ cd ../client
$ hg up -q tip
$ mkcommit newcommit
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ hg prev -q
[0da81a] commit
infinitepush: fix infinitepush pull for cgversion 3 Summary: Previously if only cgversion 3 is supported by the server, then hg up HASH may fail if _rebundle() is needed. This diff fixes it by implementing the same logic as upstream mercurial. It uses bundle capabilities to find out which versions client supports and it intersects it with versions that are supported by the server. This is grafted from D6655986 Test Plan: Tested in fb-hgext: ran unit-test Reviewers: Subscribers: Tasks: Tags:
2018-01-10 09:41:46 +03:00
$ mkcommit newcommit2
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ hg cloud backup
infinitepushbackup: back up commits stack-by-stack Summary: Use the new stack-by-stack commit backup for infinitepushbackup as well as commitcloud. Reviewed By: DurhamG Differential Revision: D8241380 fbshipit-source-id: 0c1481ad1ab5759ab642d0b02c7fe08523056292
2018-06-05 14:24:26 +03:00
backing up stack rooted at 0da81a72db1a
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
remote: pushing 3 commits:
infinitepush: fix infinitepush pull for cgversion 3 Summary: Previously if only cgversion 3 is supported by the server, then hg up HASH may fail if _rebundle() is needed. This diff fixes it by implementing the same logic as upstream mercurial. It uses bundle capabilities to find out which versions client supports and it intersects it with versions that are supported by the server. This is grafted from D6655986 Test Plan: Tested in fb-hgext: ran unit-test Reviewers: Subscribers: Tasks: Tags:
2018-01-10 09:41:46 +03:00
remote: 0da81a72db1a commit
remote: 5f9d85f9e1c6 newcommit
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
remote: c800524c1b76 newcommit2
commitcloud: backed up 2 commits
$ hg cloud check -r .
c800524c1b7637c6f3f997d1459237d01fe1ea10 backed up
infinitepush: fix infinitepush pull for cgversion 3 Summary: Previously if only cgversion 3 is supported by the server, then hg up HASH may fail if _rebundle() is needed. This diff fixes it by implementing the same logic as upstream mercurial. It uses bundle capabilities to find out which versions client supports and it intersects it with versions that are supported by the server. This is grafted from D6655986 Test Plan: Tested in fb-hgext: ran unit-test Reviewers: Subscribers: Tasks: Tags:
2018-01-10 09:41:46 +03:00
Pull just one head to trigger rebundle
$ cd ../client2
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ hg pull -r c800524c1b7637c6f3f997d1459237d01fe1ea10
infinitepush: fix infinitepush pull for cgversion 3 Summary: Previously if only cgversion 3 is supported by the server, then hg up HASH may fail if _rebundle() is needed. This diff fixes it by implementing the same logic as upstream mercurial. It uses bundle capabilities to find out which versions client supports and it intersects it with versions that are supported by the server. This is grafted from D6655986 Test Plan: Tested in fb-hgext: ran unit-test Reviewers: Subscribers: Tasks: Tags:
2018-01-10 09:41:46 +03:00
pulling from ssh://user@dummy/repo
searching for changes
adding changesets
adding manifests
adding file changes
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
added 1 changesets with 1 changes to 2 files
new changesets c800524c1b76
Reference in New Issue Copy Permalink