diff tests/test-wireproto-exchangev2-shallow.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

--- a/tests/test-wireproto-exchangev2-shallow.t	Thu Jan 14 04:56:29 2021 +0100
+++ b/tests/test-wireproto-exchangev2-shallow.t	Fri Jan 15 12:41:38 2021 +0100
@@ -168,6 +168,7 @@
    dir1/f: remote created -> g
   getting dir1/f
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  updating the branch cache
   (sent 5 HTTP requests and * bytes; received * bytes in responses) (glob)
 
   $ sqlite3 -line client-shallow-1/.hg/store/db.sqlite << EOF
@@ -333,6 +334,7 @@
    dir0/d: remote created -> g
   getting dir0/d
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  updating the branch cache
   (sent 5 HTTP requests and * bytes; received * bytes in responses) (glob)
 
   $ sqlite3 -line client-shallow-narrow-1/.hg/store/db.sqlite << EOF
@@ -469,6 +471,7 @@
    dir1/f: remote created -> g
   getting dir1/f
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  updating the branch cache
   (sent 6 HTTP requests and * bytes; received * bytes in responses) (glob)
 
 Incremental pull of shallow clone fetches new changesets