# HG changeset patch
# User Anton Shestakov <av6@dwimlabs.net>
# Date 1718279102 -14400
# Node ID ccc8352c71339b2a8c85ef08c9cc28eedff209b6
# Parent  c81bb5135307de3abab4681d84103a063b054870
topic: add more branchcache entries to test-topic-flow-publish-flag.t

It seems these new entries started appearing after the recent-ish refactoring
of branchcache in core. Now the server and the client have the same branch
cache data on disk, which is probably for the best.

The actual output with changeset hashes is:
branch2-base:c0155e8ec55a9b46d415d5b13a319d0c80e26e9d o double//slash
branch2-immutable:c0155e8ec55a9b46d415d5b13a319d0c80e26e9d o double//slash
branch2-served:256a2cb64fd8ada4ff18d57606d212f094cb50fb o double//slash

c0155e8ec55a is public, so it's correct to be in "base" and "immutable" repo
views. 256a2cb64fd8 is draft (without topic), so it's expected to be in the
"served" view.

diff -r c81bb5135307 -r ccc8352c7133 tests/test-topic-flow-publish-flag.t
--- a/tests/test-topic-flow-publish-flag.t	Sat Mar 16 18:27:18 2024 -0300
+++ b/tests/test-topic-flow-publish-flag.t	Thu Jun 13 15:45:02 2024 +0400
@@ -439,9 +439,12 @@
 
   $ cd $TESTTMP/bare-client/.hg/cache/
   $ grep double branch2* | sort
+  branch2-base:* o double//slash (glob) (hg68 !)
   branch2-immutable:* o double//slash (glob)
+  branch2-served:* o double//slash (glob) (hg68 !)
 
   $ cd $TESTTMP/bare-branch-server/.hg/cache/
   $ grep double branch2* | sort
   branch2-base:* o double//slash (glob)
   branch2-immutable:* o double//slash (glob)
+  branch2-served:* o double//slash (glob) (hg68 !)