Re: [PATCH v2 0/6] pack-objects: create new name-hash algorithm
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 4, 2024, 21:17 UTC
- Message-ID
- <xmqqiku7d0ut.fsf@gitster.g>
- In-Reply-To
- <pull.1785.v2.git.1726692381.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 12 quoted lines
> I've been focused recently on understanding and mitigating the growth of a > few internal repositories. Some of these are growing much larger than > expected for the number of contributors, and there are multiple aspects to > why this growth is so large. > ... > Derrick Stolee (6): > pack-objects: add --full-name-hash option > repack: test --full-name-hash option > pack-objects: add GIT_TEST_FULL_NAME_HASH > git-repack: update usage to match docs > p5313: add size comparison test > test-tool: add helper for name-hash values
Recent CI jobs on 'seen' has been failing the leak-check jobs, e.g.
https://github.com/git/git/actions/runs/11184876759/job/31096601111#step:4:1886
shows that t5310 and t5334 are having problems.
I randomly picked this topic and ejected it out of 'seen', and the result is fairing a bit better. t5310 that failed 228/228 subtests in the above run is now passing. I didn't run this topic alone under the leak checker, so it is entirely possible that there are some unfortunate interactions with other topics in flight.
t5334 still fails 8/16 subtests just like the above run, exonerating this topic for its breakage.
https://github.com/git/git/actions/runs/11186737635/job/31102378478#step:4:1880