--- a/tests/test-keyword.t Mon Jan 07 23:30:00 2013 +0000
+++ b/tests/test-keyword.t Thu Jan 10 16:02:08 2013 +0000
@@ -576,6 +576,7 @@
Commit and show expansion in original and copy
$ hg --debug commit -ma2c -d '1 0' -u 'User Name <user@example.com>'
+ invalid branchheads cache (unserved): tip differs
c
c: copy a:0045e12f6c5791aac80ca6cbfd97709a88307292
overwriting c expanding keywords
@@ -746,10 +747,23 @@
Commit with multi-line message and custom expansion
+|Note:
+|
+| After the last rollback, the "unserved" branchheads cache became invalid, but
+| all changeset in the repo were public. So filtering wise:
+| "mutable" == "unserved" == ΓΈ.
+|
+| As the "unserved" cache is invalid, we fall back to "mutable" cache. But not
+| update is needed between "mutable" and "unserved" cache and the "unserved"
+| cache is not updated on disk. The on disk version therefor stay invalid for
+| some time. This explains why the "unserved" branchheads cache is detect
+| invalid here.
+
$ hg --debug commit -l log -d '2 0' -u 'User Name <user@example.com>'
- invalid branchheads cache: tip differs
+ invalid branchheads cache (unserved): tip differs
a
invalid branchheads cache: tip differs
+ invalid branchheads cache (unserved): tip differs
overwriting a expanding keywords
committed changeset 2:bb948857c743469b22bbf51f7ec8112279ca5d83
$ rm log
@@ -792,7 +806,6 @@
$ hg remove a
$ hg --debug commit -m rma
invalid branchheads cache: tip differs
- invalid branchheads cache: tip differs
committed changeset 3:d14c712653769de926994cf7fbb06c8fbd68f012
$ hg status
? c
@@ -903,7 +916,6 @@
[255]
$ cd x
$ hg --debug commit -m xa -d '3 0' -u 'User Name <user@example.com>'
- invalid branchheads cache: tip differs
x/a
x/a: copy a:779c764182ce5d43e2b1eb66ce06d7b47bfe342e
invalid branchheads cache: tip differs