RE: [BUG] 2.46.0 t7701.09 fails on NonStop ia64

[<rsbecker@nexbridge.com>]

>-----Original Message-----
>From: Taylor Blau <me@ttaylorr.com>
>Sent: Sunday, August 4, 2024 12:03 PM
>To: rsbecker@nexbridge.com
>Cc: git@vger.kernel.org
>Subject: Re: [BUG] 2.46.0 t7701.09 fails on NonStop ia64
>
>On Fri, Aug 02, 2024 at 06:07:55PM -0400, rsbecker@nexbridge.com wrote:
>> After the first repack, I have the following idx files. No foo/bar/baz inside.
>> The generate_random_blob() does generate the proper amount of bytes.
>> I tried changing 0xff to 0x00ff at the putchar just in case we had bad
>> sign extension - that wasn't it.
>
>Hmm. What is in these index files if not the three randomly generated objects? Can
>you run show-index instead and share the results of that on the pack(s) in your
>repository after the first repack, and share the results with the list?
>
>I think those would be more readable than a hexdump, especially if your machine
>random source is different than mine (in which case I can't guess the values of $foo,
>$bar, and $baz).

After git repack -d --cruft --max-cruft-size=1M &&...

./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index < .git/objects/pack/pack-68c6c8c8538900694c32380ac1484201c8b60d8d.pack
fatal: unable to read index
./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index < .git/objects/pack/pack-8f53f837597ebbdfc6f8ed173349e5cecbcfb97e.pack
fatal: corrupt index file
./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index < .git/objects/pack/pack-b8dc9aadaadc12c82b0053fdee0039ae1025a8f8.pack
fatal: corrupt index file
./trash directory.t7704-repack-cruft/max-cruft-size-prune: git show-index < .git/objects/pack/pack-c2357b2b204fda52bc1f5515de94227e1db012af.pack
fatal: corrupt index file

Apparently, something is wrong. This is an ia64 Big Endian. Not sure that matters.