Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
mercurial-devel
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
mercurial
mercurial-devel
Commits
99eb9f26
Commit
99eb9f26
authored
6 years ago
by
Pierre-Yves David
Browse files
Options
Downloads
Patches
Plain Diff
manifestcache: test that adding the same entry twice do not duplicates it
Simple sanity check.
parent
1e75311d
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tests/test-manifest.t
+8
-0
8 additions, 0 deletions
tests/test-manifest.t
with
8 additions
and
0 deletions
tests/test-manifest.t
+
8
−
0
View file @
99eb9f26
...
...
@@ -116,3 +116,11 @@
cache
contains
1
manifest
entries
,
in
order
of
most
to
least
recent:
id:
1e01206
b1d2f72bd55f2a33fa8ccad74144825b7
,
size
133
bytes
total
cache
data
size
157
bytes
,
on
-
disk
157
bytes
Check
we
don
'
t duplicated entry (added from the debug command)
$ hg debugmanifestfulltextcache --add 1e01206b1d2f72bd55f2a33fa8ccad74144825b7
$ hg debugmanifestfulltextcache
cache contains 1 manifest entries, in order of most to least recent:
id: 1e01206b1d2f72bd55f2a33fa8ccad74144825b7, size 133 bytes
total cache data size 157 bytes, on-disk 157 bytes
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment