Mercurial > hg
view tests/test-remotefilelog-bad-configs.t @ 42712:cdf0e9523de1
branchmap: explicitly warm+write all subsets of the branchmap caches
'full' claims it will warm all of the caches that are known about, but this was
not the case - it did not actually warm the branchmap caches for subsets that we
haven't requested, or for subsets that are still considered "valid". By
explicitly writing them to disk, we can force the subsets for ex: "served" to be
written ("immutable" and "base"), making it cheaper to calculate "served" the
next time it needs to be updated.
Differential Revision: https://phab.mercurial-scm.org/D6710
author | Kyle Lippincott <spectral@google.com> |
---|---|
date | Mon, 05 Aug 2019 13:31:12 -0700 |
parents | 0800d9e6e216 |
children |
line wrap: on
line source
#require no-windows $ . "$TESTDIR/remotefilelog-library.sh" $ hg init master $ cd master $ cat >> .hg/hgrc <<EOF > [remotefilelog] > server=True > EOF $ echo x > x $ echo y > y $ echo z > z $ hg commit -qAm xy $ cd .. $ hgcloneshallow ssh://user@dummy/master shallow -q 3 files fetched over 1 fetches - (3 misses, 0.00% hit ratio) over *s (glob) $ cd shallow Verify error message when noc achepath specified $ hg up -q null $ cp $HGRCPATH $HGRCPATH.bak $ grep -v cachepath < $HGRCPATH.bak > tmp $ mv tmp $HGRCPATH $ hg up tip abort: could not find config option remotefilelog.cachepath [255] $ mv $HGRCPATH.bak $HGRCPATH Verify error message when no fallback specified $ hg up -q null $ rm .hg/hgrc $ clearcache $ hg up tip 3 files fetched over 1 fetches - (3 misses, 0.00% hit ratio) over *s (glob) abort: no remotefilelog server configured - is your .hg/hgrc trusted? [255]