Skip to content
Snippets Groups Projects
Commit d881c072 authored by Mads Kiilerich's avatar Mads Kiilerich
Browse files

largefiles: test coverage of handling of store corruption

This reveals that update might put a corrupted largefile in the working
directory where it will show up as modified and ready for commit.
parent 27683c63
No related branches found
No related tags found
No related merge requests found
......@@ -179,3 +179,25 @@
$ find src/.hg/largefiles/* | egrep "(dirstate|$hash)" | sort
src/.hg/largefiles/dirstate
src/.hg/largefiles/e2fb5f2139d086ded2cb600d5a91a196e76bf020
Inject corruption into the largefiles store and see how update handles that:
$ cd src
$ hg up -qC
$ cat large
modified
$ rm large
$ cat .hglf/large
e2fb5f2139d086ded2cb600d5a91a196e76bf020
$ mv .hg/largefiles/e2fb5f2139d086ded2cb600d5a91a196e76bf020 ..
$ echo corruption > .hg/largefiles/e2fb5f2139d086ded2cb600d5a91a196e76bf020
(the following update will put the corrupted file into the working directory
where it will show up as a change)
$ hg up -C
getting changed largefiles
1 largefiles updated, 0 removed
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg st
M large
? z
$ rm .hg/largefiles/e2fb5f2139d086ded2cb600d5a91a196e76bf020
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment