From: Taylor Blau <me@ttaylorr.com>
To: rsbecker@nexbridge.com
Cc: git@vger.kernel.org
Subject: Re: [BUG] 2.46.0 t7701.09 fails on NonStop ia64
Date: Sun, 4 Aug 2024 12:02:31 -0400 [thread overview]
Message-ID: <Zq+mF2fyL5hux+3k@nand.local> (raw)
In-Reply-To: <040801dae528$70966d10$51c34730$@nexbridge.com>
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).
Thanks,
Taylor
next prev parent reply other threads:[~2024-08-04 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 18:03 [BUG] 2.46.0 t7701.09 fails on NonStop ia64 rsbecker
2024-08-01 19:23 ` Taylor Blau
2024-08-01 22:25 ` rsbecker
2024-08-02 0:58 ` Taylor Blau
2024-08-02 1:51 ` rsbecker
2024-08-02 22:07 ` rsbecker
2024-08-04 16:02 ` Taylor Blau [this message]
2024-08-04 16:15 ` rsbecker
2024-08-04 16:19 ` Taylor Blau
2024-08-04 16:38 ` rsbecker
2024-08-04 18:12 ` Taylor Blau
2024-08-04 19:15 ` rsbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zq+mF2fyL5hux+3k@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).