diff tests/test-parseindex.t @ 51181:dcaa2df1f688

changelog: never inline changelog

The test suite mostly use small repositories, that implies that most changelog in the
tests are inlined. As a result, non-inlined changelog are quite poorly tested.
Since non-inline changelog are most common case for serious repositories, this
lack of testing is a significant problem that results in high profile issue like
the one recently fixed by 66417f55ea33 and 849745d7da89.

Inlining the changelog does not bring much to the table, the number of total
file saved is negligible, and the changelog will be read by most operation
anyway.

So this changeset is make it so we never inline the changelog, and de-inline the
one that are still inlined whenever we touch them.

By doing that, we remove the "dual code path" situation for writing new entry to
the changelog and move to a "single code path" situation. Having a single
code path simplify the code and make sure it is covered by test (if test cover
that situation obviously)


This impact all tests that care about the number of file and the exchange size,
but there is nothing too complicated in them just a lot of churn.

The churn is made "worse" by the fact rust will use the persistent nodemap on
any changelog now. Which is overall a win as it means testing the persistent
nodemap more and having less special cases.

In short, having inline changelog is mostly useless and an endless source of
pain. We get rid of it.

--- a/tests/test-parseindex.t	Mon Dec 11 11:50:55 2023 +0100
+++ b/tests/test-parseindex.t	Mon Dec 11 22:27:59 2023 +0100
@@ -145,8 +145,8 @@
   > ]
   > for n, p in poisons:
   >     # corrupt p1 at rev0 and p2 at rev1
-  >     rev_0 = data[:64 + 63]
-  >     rev_1 = data[64 + 63:]
+  >     rev_0 = data[:64]
+  >     rev_1 = data[64:]
   >     altered_rev_0 = rev_0[:24] + p + rev_0[24 + 4:]
   >     altered_rev_1 = rev_1[:28] + p + rev_1[28 + 4:]
   >     new_data = altered_rev_0 + altered_rev_1