test: enable sparse-revlog for test-lfs-serve.t
authorBoris Feld <boris.feld@octobus.net>
Mon, 12 Nov 2018 01:09:19 +0100
changeset 53663 0e21db2458f4bd49875656403f78ac83f0620f1a
parent 53662 c35d3cb758a467a4f1e754b3d8a7a41f4f3f24f3
child 53664 eecc7a2ebf52e8a1dedb942008c0e2973b3af241
push id1079
push usergszorc@mozilla.com
push dateMon, 10 Dec 2018 19:44:59 +0000
test: enable sparse-revlog for test-lfs-serve.t We are about to enable sparse-revlog globally. To help with reviewing the tests change, we isolate them in individual changesets. Differential Revision: https://phab.mercurial-scm.org/D5324
tests/test-lfs-serve.t
--- a/tests/test-lfs-serve.t
+++ b/tests/test-lfs-serve.t
@@ -1,8 +1,14 @@
+TRANSITIONAL CONFIG
+  $ cat << EOF >> $HGRCPATH
+  > [format]
+  > sparse-revlog = yes
+  > EOF
+
 #testcases lfsremote-on lfsremote-off
 #require serve no-reposimplestore no-chg
 
 This test splits `hg serve` with and without using the extension into separate
 tests cases.  The tests are broken down as follows, where "LFS"/"No-LFS"
 indicates whether or not there are commits that use an LFS file, and "D"/"E"
 indicates whether or not the extension is loaded.  The "X" cases are not tested
 individually, because the lfs requirement causes the process to bail early if
@@ -126,17 +132,17 @@ non-lfs content, and the extension enabl
   --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
   +++ b/nonlfs.txt	Thu Jan 01 00:00:00 1970 +0000
   @@ -0,0 +1,1 @@
   +non-lfs
   *** runcommand debugupgraderepo -q --run
   upgrade will perform the following actions:
   
   requirements
-     preserved: dotencode, fncache, generaldelta, revlogv1, store
+     preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store
   
   beginning upgrade...
   repository locked and read-only
   creating temporary repository to stage migrated data: * (glob)
   (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 324 bytes in store; 129 bytes tracked data
   migrating 1 filelogs containing 1 revisions (73 bytes in store; 8 bytes tracked data)