This is an archive of the discontinued Mercurial Phabricator instance.

Differential D8427

upgrade: properly filter action depending on planned work
ClosedPublic

Authored by marmoute on Apr 15 2020, 4:16 PM.

Details

Reviewers
Alphare
Group Reviewers
hg-reviewers
Commits
rHGc36a3fcfc36b: upgrade: properly filter action depending on planned work
Summary

The determineactions function filters out deficiency that are not scheduled to
be fixed by the target repository configuration. However it only did so for
requirement we currently support, letting other actions for unsupported
requirement through even if the target repo configuration did not request it.

As a result the output of the command was easily polluted by experimental
feature with no upgrade support.

We rework the code to still filter out requirement based action without the
faulty filtering.

Diff Detail

Repository
rHG Mercurial
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Revision Contents
Changeset List

PathPackages
Mmercurial/upgrade.py (6 lines)
Mtests/test-lfs-serve.t (6 lines)
Mtests/test-upgrade-repo.t (114 lines)

Diff 21204

mercurial/upgrade.py

The role of this function is to filter improvements if needed, apply The role of this function is to filter improvements if needed, apply
recommended optimizations from the improvements list that make sense, recommended optimizations from the improvements list that make sense,
etc. etc.
Returns a list of action names. Returns a list of action names.
""" """
newactions = [] newactions = []
knownreqs = supporteddestrequirements(repo)
for d in deficiencies: for d in deficiencies:
name = d.name name = d._requirement
# If the action is a requirement that doesn't show up in the # If the action is a requirement that doesn't show up in the
# destination requirements, prune the action. # destination requirements, prune the action.
if name in knownreqs and name not in destreqs: if name is not None and name not in destreqs:
continue continue
newactions.append(d) newactions.append(d)
# FUTURE consider adding some optimizations here for certain transitions. # FUTURE consider adding some optimizations here for certain transitions.
# e.g. adding generaldelta could schedule parent redeltas. # e.g. adding generaldelta could schedule parent redeltas.
return newactions return newactions

tests/test-lfs-serve.t

@@ -0,0 +1,1 @@ @@ -0,0 +1,1 @@
+non-lfs +non-lfs
*** runcommand debugupgraderepo -q --run *** runcommand debugupgraderepo -q --run
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: * (glob) creating temporary repository to stage migrated data: * (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog) migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog)
migrating 324 bytes in store; 129 bytes tracked data migrating 324 bytes in store; 129 bytes tracked data
migrating 1 filelogs containing 1 revisions (73 bytes in store; 8 bytes tracked data) migrating 1 filelogs containing 1 revisions (73 bytes in store; 8 bytes tracked data)
finished migrating 1 filelog revisions across 1 filelogs; change in size: 0 bytes finished migrating 1 filelog revisions across 1 filelogs; change in size: 0 bytes

tests/test-upgrade-repo.t

] ]
$ hg debugupgraderepo $ hg debugupgraderepo
(no feature deficiencies found in existing repository) (no feature deficiencies found in existing repository)
performing an upgrade with "--run" will make the following changes: performing an upgrade with "--run" will make the following changes:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
additional optimizations are available by specifying "--optimize <name>": additional optimizations are available by specifying "--optimize <name>":
re-delta-parent re-delta-parent
deltas within internal storage will be recalculated to choose an optimal base revision where this was not already done; the size of the repository may shrink and various operations may become faster; the first time this optimization is performed could slow down upgrade execution considerably; subsequent invocations should not run noticeably slower deltas within internal storage will be recalculated to choose an optimal base revision where this was not already done; the size of the repository may shrink and various operations may become faster; the first time this optimization is performed could slow down upgrade execution considerably; subsequent invocations should not run noticeably slower
re-delta-multibase re-delta-multibase
deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges
re-delta-all re-delta-all
deltas within internal storage will always be recalculated without reusing prior deltas; this will likely make execution run several times slower; this optimization is typically not needed deltas within internal storage will always be recalculated without reusing prior deltas; this will likely make execution run several times slower; this optimization is typically not needed
re-delta-fulladd re-delta-fulladd
every revision will be re-added as if it was new content. It will go through the full storage mechanism giving extensions a chance to process it (eg. lfs). This is similar to "re-delta-all" but even slower since more logic is involved. every revision will be re-added as if it was new content. It will go through the full storage mechanism giving extensions a chance to process it (eg. lfs). This is similar to "re-delta-all" but even slower since more logic is involved.
--optimize can be used to add optimizations --optimize can be used to add optimizations
$ hg debugupgrade --optimize redeltaparent $ hg debugupgrade --optimize redeltaparent
(no feature deficiencies found in existing repository) (no feature deficiencies found in existing repository)
performing an upgrade with "--run" will make the following changes: performing an upgrade with "--run" will make the following changes:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
additional optimizations are available by specifying "--optimize <name>": additional optimizations are available by specifying "--optimize <name>":
re-delta-multibase re-delta-multibase
deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges
re-delta-all re-delta-all
deltas within internal storage will always be recalculated without reusing prior deltas; this will likely make execution run several times slower; this optimization is typically not needed deltas within internal storage will always be recalculated without reusing prior deltas; this will likely make execution run several times slower; this optimization is typically not needed
re-delta-fulladd re-delta-fulladd
every revision will be re-added as if it was new content. It will go through the full storage mechanism giving extensions a chance to process it (eg. lfs). This is similar to "re-delta-all" but even slower since more logic is involved. every revision will be re-added as if it was new content. It will go through the full storage mechanism giving extensions a chance to process it (eg. lfs). This is similar to "re-delta-all" but even slower since more logic is involved.
modern form of the option modern form of the option
$ hg debugupgrade --optimize re-delta-parent $ hg debugupgrade --optimize re-delta-parent
(no feature deficiencies found in existing repository) (no feature deficiencies found in existing repository)
performing an upgrade with "--run" will make the following changes: performing an upgrade with "--run" will make the following changes:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
additional optimizations are available by specifying "--optimize <name>": additional optimizations are available by specifying "--optimize <name>":
re-delta-multibase re-delta-multibase
deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges
repository will be better able to store files beginning with a space or period repository will be better able to store files beginning with a space or period
generaldelta generaldelta
repository storage will be able to create optimal deltas; new repository data will be smaller and read times should decrease; interacting with other repositories using this storage model should require less network and CPU resources, making "hg push" and "hg pull" faster repository storage will be able to create optimal deltas; new repository data will be smaller and read times should decrease; interacting with other repositories using this storage model should require less network and CPU resources, making "hg push" and "hg pull" faster
sparserevlog sparserevlog
Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server. Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server.
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
additional optimizations are available by specifying "--optimize <name>": additional optimizations are available by specifying "--optimize <name>":
re-delta-parent re-delta-parent
deltas within internal storage will be recalculated to choose an optimal base revision where this was not already done; the size of the repository may shrink and various operations may become faster; the first time this optimization is performed could slow down upgrade execution considerably; subsequent invocations should not run noticeably slower deltas within internal storage will be recalculated to choose an optimal base revision where this was not already done; the size of the repository may shrink and various operations may become faster; the first time this optimization is performed could slow down upgrade execution considerably; subsequent invocations should not run noticeably slower
re-delta-multibase re-delta-multibase
deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges
repository will be more resilient to storing certain paths and performance of certain operations should be improved repository will be more resilient to storing certain paths and performance of certain operations should be improved
generaldelta generaldelta
repository storage will be able to create optimal deltas; new repository data will be smaller and read times should decrease; interacting with other repositories using this storage model should require less network and CPU resources, making "hg push" and "hg pull" faster repository storage will be able to create optimal deltas; new repository data will be smaller and read times should decrease; interacting with other repositories using this storage model should require less network and CPU resources, making "hg push" and "hg pull" faster
sparserevlog sparserevlog
Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server. Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server.
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
additional optimizations are available by specifying "--optimize <name>": additional optimizations are available by specifying "--optimize <name>":
re-delta-parent re-delta-parent
deltas within internal storage will be recalculated to choose an optimal base revision where this was not already done; the size of the repository may shrink and various operations may become faster; the first time this optimization is performed could slow down upgrade execution considerably; subsequent invocations should not run noticeably slower deltas within internal storage will be recalculated to choose an optimal base revision where this was not already done; the size of the repository may shrink and various operations may become faster; the first time this optimization is performed could slow down upgrade execution considerably; subsequent invocations should not run noticeably slower
re-delta-multibase re-delta-multibase
deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges deltas within internal storage will be recalculated against multiple base revision and the smallest difference will be used; the size of the repository may shrink significantly when there are many merges; this optimization will slow down execution in proportion to the number of merges in the repository and the amount of files in the repository; this slow down should not be significant unless there are tens of thousands of files and thousands of merges
$ hg init modern $ hg init modern
$ hg -R modern debugupgraderepo --run $ hg -R modern debugupgraderepo --run
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/modern/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/modern/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
data fully migrated to temporary repository data fully migrated to temporary repository
marking source repository as being upgraded; clients will be unable to read from repository marking source repository as being upgraded; clients will be unable to read from repository
starting in-place swap of repository data starting in-place swap of repository data
replaced files will be backed up at $TESTTMP/modern/.hg/upgradebackup.* (glob) replaced files will be backed up at $TESTTMP/modern/.hg/upgradebackup.* (glob)
requirements requirements
preserved: dotencode, fncache, revlogv1, store preserved: dotencode, fncache, revlogv1, store
added: generaldelta added: generaldelta
generaldelta generaldelta
repository storage will be able to create optimal deltas; new repository data will be smaller and read times should decrease; interacting with other repositories using this storage model should require less network and CPU resources, making "hg push" and "hg pull" faster repository storage will be able to create optimal deltas; new repository data will be smaller and read times should decrease; interacting with other repositories using this storage model should require less network and CPU resources, making "hg push" and "hg pull" faster
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
migrating 519 KB in store; 1.05 MB tracked data migrating 519 KB in store; 1.05 MB tracked data
migrating 3 filelogs containing 3 revisions (518 KB in store; 1.05 MB tracked data) migrating 3 filelogs containing 3 revisions (518 KB in store; 1.05 MB tracked data)
finished migrating 3 filelog revisions across 3 filelogs; change in size: 0 bytes finished migrating 3 filelog revisions across 3 filelogs; change in size: 0 bytes
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, store preserved: dotencode, fncache, generaldelta, revlogv1, store
added: sparserevlog added: sparserevlog
sparserevlog sparserevlog
Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server. Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server.
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
migrating 519 KB in store; 1.05 MB tracked data migrating 519 KB in store; 1.05 MB tracked data
migrating 3 filelogs containing 3 revisions (518 KB in store; 1.05 MB tracked data) migrating 3 filelogs containing 3 revisions (518 KB in store; 1.05 MB tracked data)
finished migrating 3 filelog revisions across 3 filelogs; change in size: 0 bytes finished migrating 3 filelog revisions across 3 filelogs; change in size: 0 bytes
We can restrict optimization to some revlog: We can restrict optimization to some revlog:
$ hg debugupgrade --optimize re-delta-parent --run --manifest --no-backup --debug --traceback $ hg debugupgrade --optimize re-delta-parent --run --manifest --no-backup --debug --traceback
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
Check we can select negatively Check we can select negatively
$ hg debugupgrade --optimize re-delta-parent --run --no-manifest --no-backup --debug --traceback $ hg debugupgrade --optimize re-delta-parent --run --no-manifest --no-backup --debug --traceback
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
Check that we can select changelog only Check that we can select changelog only
$ hg debugupgrade --optimize re-delta-parent --run --changelog --no-backup --debug --traceback $ hg debugupgrade --optimize re-delta-parent --run --changelog --no-backup --debug --traceback
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
Check that we can select filelog only Check that we can select filelog only
$ hg debugupgrade --optimize re-delta-parent --run --no-changelog --no-manifest --no-backup --debug --traceback $ hg debugupgrade --optimize re-delta-parent --run --no-changelog --no-manifest --no-backup --debug --traceback
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
$ hg debugupgrade --optimize re-delta-parent --run --manifest --no-backup --debug --traceback $ hg debugupgrade --optimize re-delta-parent --run --manifest --no-backup --debug --traceback
ignoring revlogs selection flags, format requirements change: sparserevlog ignoring revlogs selection flags, format requirements change: sparserevlog
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, store preserved: dotencode, fncache, generaldelta, revlogv1, store
removed: sparserevlog removed: sparserevlog
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, store preserved: dotencode, fncache, generaldelta, revlogv1, store
added: sparserevlog added: sparserevlog
sparserevlog sparserevlog
Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server. Revlog supports delta chain with more unused data between payload. These gaps will be skipped at read time. This allows for better delta chains, making a better compression and faster exchange with server.
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-parent re-delta-parent
deltas within internal storage will choose a new base revision if needed deltas within internal storage will choose a new base revision if needed
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/upgradegd/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)
$ touch .hg/store/.XX_special_filename $ touch .hg/store/.XX_special_filename
$ hg debugupgraderepo --run $ hg debugupgraderepo --run
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/store-filenames/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/store-filenames/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog) migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog)
migrating 301 bytes in store; 107 bytes tracked data migrating 301 bytes in store; 107 bytes tracked data
migrating 1 filelogs containing 1 revisions (64 bytes in store; 0 bytes tracked data) migrating 1 filelogs containing 1 revisions (64 bytes in store; 0 bytes tracked data)
finished migrating 1 filelog revisions across 1 filelogs; change in size: 0 bytes finished migrating 1 filelog revisions across 1 filelogs; change in size: 0 bytes
copy of old repository backed up at $TESTTMP/store-filenames/.hg/upgradebackup.* (glob) copy of old repository backed up at $TESTTMP/store-filenames/.hg/upgradebackup.* (glob)
the old repository will not be deleted; remove it to free up disk space once the upgraded repository is verified the old repository will not be deleted; remove it to free up disk space once the upgraded repository is verified
$ hg debugupgraderepo --run --optimize redeltafulladd $ hg debugupgraderepo --run --optimize redeltafulladd
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-fulladd re-delta-fulladd
each revision will be added as new content to the internal storage; this will likely drastically slow down execution time, but some extensions might need it each revision will be added as new content to the internal storage; this will likely drastically slow down execution time, but some extensions might need it
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/store-filenames/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/store-filenames/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog) migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog)
store store
$ hg debugupgraderepo --run $ hg debugupgraderepo --run
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, largefiles, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, largefiles, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/largefilesrepo/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/largefilesrepo/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog) migrating 3 total revisions (1 in filelogs, 1 in manifests, 1 in changelog)
migrating 355 bytes in store; 160 bytes tracked data migrating 355 bytes in store; 160 bytes tracked data
migrating 1 filelogs containing 1 revisions (106 bytes in store; 41 bytes tracked data) migrating 1 filelogs containing 1 revisions (106 bytes in store; 41 bytes tracked data)
finished migrating 1 filelog revisions across 1 filelogs; change in size: 0 bytes finished migrating 1 filelog revisions across 1 filelogs; change in size: 0 bytes
.hg/store/lfs/objects/d0/beab232adff5ba365880366ad30b1edb85c4c5372442b5d2fe27adc96d653f .hg/store/lfs/objects/d0/beab232adff5ba365880366ad30b1edb85c4c5372442b5d2fe27adc96d653f
$ hg debugupgraderepo --run $ hg debugupgraderepo --run
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, largefiles, lfs, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, largefiles, lfs, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/largefilesrepo/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/largefilesrepo/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 6 total revisions (2 in filelogs, 2 in manifests, 2 in changelog) migrating 6 total revisions (2 in filelogs, 2 in manifests, 2 in changelog)
migrating 801 bytes in store; 467 bytes tracked data migrating 801 bytes in store; 467 bytes tracked data
migrating 2 filelogs containing 2 revisions (296 bytes in store; 182 bytes tracked data) migrating 2 filelogs containing 2 revisions (296 bytes in store; 182 bytes tracked data)
finished migrating 2 filelog revisions across 2 filelogs; change in size: 0 bytes finished migrating 2 filelog revisions across 2 filelogs; change in size: 0 bytes
2 1 2 0 other 30 200 107 0.53500 128 21 0.19626 128 128 0.83594 1 2 1 2 0 other 30 200 107 0.53500 128 21 0.19626 128 128 0.83594 1
$ hg debugupgraderepo --run --optimize redeltaall $ hg debugupgraderepo --run --optimize redeltaall
upgrade will perform the following actions: upgrade will perform the following actions:
requirements requirements
preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
sidedata
Allows storage of extra data alongside a revision.
copies-sdc
Allows to use more efficient algorithm to deal with copy tracing.
re-delta-all re-delta-all
deltas within internal storage will be fully recomputed; this will likely drastically slow down execution time deltas within internal storage will be fully recomputed; this will likely drastically slow down execution time
beginning upgrade... beginning upgrade...
repository locked and read-only repository locked and read-only
creating temporary repository to stage migrated data: $TESTTMP/localconfig/.hg/upgrade.* (glob) creating temporary repository to stage migrated data: $TESTTMP/localconfig/.hg/upgrade.* (glob)
(it is safe to interrupt this process any time before data migration completes) (it is safe to interrupt this process any time before data migration completes)
migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog) migrating 9 total revisions (3 in filelogs, 3 in manifests, 3 in changelog)