diff tests/test-stream-bundle-v2.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 181ee2118a96
children 84a93fa7ecfd
line wrap: on
line diff
--- a/tests/test-stream-bundle-v2.t	Thu Jan 14 04:56:29 2021 +0100
+++ b/tests/test-stream-bundle-v2.t	Fri Jan 15 12:41:38 2021 +0100
@@ -117,6 +117,7 @@
    E: remote created -> g
   getting E
   5 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  updating the branch cache
   (sent 4 HTTP requests and * bytes; received * bytes in responses) (glob)
 
   $ hg clone --stream http://localhost:$HGPORT streamv2-clone-explicit --debug
@@ -173,4 +174,5 @@
    E: remote created -> g
   getting E
   5 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  updating the branch cache
   (sent 4 HTTP requests and * bytes; received * bytes in responses) (glob)