diff tests/test-share.t @ 46314:95a615dd77bf

clone: make sure we warm the cache after a clone This work around any deviciency/limitation of the clone process. In our case this ensure the persistent nodemap exist with valid content. Ideally, the cloning process would also do "the right thing". However since older server will never be able to do "the right thing". The local workaround will be necessary anyway. I am not worried by the performance impact of this as `hg clone` is non-instant on large repositories where is could matters. Warming the cache if they are already correct is very fast. And if they are not already warm, this seems like a good time to do so. This impact various test as more cache are now warmed sooner, all the change should be harmless. Differential Revision: https://phab.mercurial-scm.org/D9789
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Fri, 15 Jan 2021 12:41:38 +0100
parents 5b9bb4e9a3bf
children 4b0192f592cf
line wrap: on
line diff
--- a/tests/test-share.t	Thu Jan 14 04:56:29 2021 +0100
+++ b/tests/test-share.t	Fri Jan 15 12:41:38 2021 +0100
@@ -62,9 +62,17 @@
   updating to branch default
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ ls -1 ../repo2-clone/.hg/cache
+  branch2-base
+  branch2-immutable
   branch2-served
+  branch2-served.hidden
+  branch2-visible
+  branch2-visible-hidden
+  hgtagsfnodes1
   rbc-names-v1
   rbc-revs-v1
+  tags2
+  tags2-served
   tags2-visible
 
 Some sed versions appends newline, some don't, and some just fails