From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [BUG] 2.46.0 t7701.09 fails on NonStop ia64
Date: Thu, 1 Aug 2024 14:03:31 -0400 [thread overview]
Message-ID: <02d301dae43d$2202fc90$6608f5b0$@nexbridge.com> (raw)
Hi Team,
I think this is low priority but would like to understand the situation. It
only happens on NonStop ia64 (consistently), not x86.
The t7701.09 subtest fails missing files:
Total 3 (delta 0), reused 3 (delta 0), pack-reused 0 (from 0)
ls: cannot access '.git/objects/pack/pack-*.mtimes': No such file or
directory
test_line_count: line count for cruft.after != 2
not ok 9 - --max-cruft-size with pruning
The test directory contains:
./.git/objects/pack
./.git/objects/pack/pack-68c6c8c8538900694c32380ac1484201c8b60d8d.idx
./.git/objects/pack/pack-68c6c8c8538900694c32380ac1484201c8b60d8d.pack
./.git/objects/pack/pack-68c6c8c8538900694c32380ac1484201c8b60d8d.rev
but no mtimes files. I'm not sure how to proceed with this - currently
ignoring the failure but I
think it might be significant. This only fails on NonStop ia64 (which is
much older) and passes
on NonStop x86. There is no real file system reason why this would be a
difference between the
two platforms. There are some limit differences, but that's pretty much it.
Any assistance tracking this down would be appreciated. I can set up
breakpoints to catch
whatever is needed.
Regards,
Randall
next reply other threads:[~2024-08-01 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 18:03 rsbecker [this message]
2024-08-01 19:23 ` [BUG] 2.46.0 t7701.09 fails on NonStop ia64 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
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='02d301dae43d$2202fc90$6608f5b0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
/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).