Mercurial > hg
comparison tests/test-manifest.t @ 41964:d121823072b8
manifestcache: protect write with `wlock` instead of `lock`
The `wlock` is taken by both `update` and `commit` type operation. This would
help persisting the cache more aggressively.
An explicit test is introduced. However, we can already see the effect of this
change on earlier test output.
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Fri, 15 Mar 2019 15:07:43 +0000 |
| parents | 6386f9a421d2 |
| children | 89c0c8edc9d4 |
comparison
equal
deleted
inserted
replaced
| 41963:6386f9a421d2 | 41964:d121823072b8 |
|---|---|
| 104 manifest: 0:fce2a30dedad1eef4da95ca1dc0004157aa527cf | 104 manifest: 0:fce2a30dedad1eef4da95ca1dc0004157aa527cf |
| 105 | 105 |
| 106 Showing the content of the caches after the above operations | 106 Showing the content of the caches after the above operations |
| 107 | 107 |
| 108 $ hg debugmanifestfulltextcache | 108 $ hg debugmanifestfulltextcache |
| 109 cache empty | 109 cache contains 1 manifest entries, in order of most to least recent: |
| 110 id: 1e01206b1d2f72bd55f2a33fa8ccad74144825b7, size 133 bytes | |
| 111 total cache data size 157 bytes, on-disk 157 bytes | |
| 110 | 112 |
| 111 (Clearing the cache in case of any content) | 113 (Clearing the cache in case of any content) |
| 112 | 114 |
| 113 $ hg debugmanifestfulltextcache --clear | 115 $ hg debugmanifestfulltextcache --clear |
| 114 | 116 |
| 181 id: 1e01206b1d2f72bd55f2a33fa8ccad74144825b7, size 133 bytes | 183 id: 1e01206b1d2f72bd55f2a33fa8ccad74144825b7, size 133 bytes |
| 182 total cache data size 314 bytes, on-disk 314 bytes | 184 total cache data size 314 bytes, on-disk 314 bytes |
| 183 $ hg log -r 'ancestors(., 1)' --debug | grep 'manifest:' | 185 $ hg log -r 'ancestors(., 1)' --debug | grep 'manifest:' |
| 184 manifest: 1:1e01206b1d2f72bd55f2a33fa8ccad74144825b7 | 186 manifest: 1:1e01206b1d2f72bd55f2a33fa8ccad74144825b7 |
| 185 manifest: 2:26b8653b67af8c1a0a0317c4ee8dac50a41fdb65 | 187 manifest: 2:26b8653b67af8c1a0a0317c4ee8dac50a41fdb65 |
| 188 | |
| 189 hg update should warm the cache too | |
| 190 | |
| 191 (force dirstate check to avoid flackiness in manifest order) | |
| 192 $ hg debugrebuilddirstate | |
| 193 | |
| 194 $ hg update 0 | |
| 195 0 files updated, 0 files merged, 1 files removed, 0 files unresolved | |
| 196 $ hg debugmanifestfulltextcache | |
| 197 cache contains 3 manifest entries, in order of most to least recent: | |
| 198 id: fce2a30dedad1eef4da95ca1dc0004157aa527cf, size 87 bytes | |
| 199 id: 26b8653b67af8c1a0a0317c4ee8dac50a41fdb65, size 133 bytes | |
| 200 id: 1e01206b1d2f72bd55f2a33fa8ccad74144825b7, size 133 bytes | |
| 201 total cache data size 425 bytes, on-disk 425 bytes | |
| 202 $ hg log -r '0' --debug | grep 'manifest:' | |
| 203 manifest: 0:fce2a30dedad1eef4da95ca1dc0004157aa527cf |