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: Thu, 1 Aug 2024 15:23:05 -0400 [thread overview]
Message-ID: <ZqvgmYl8BTYvsSa0@nand.local> (raw)
In-Reply-To: <02d301dae43d$2202fc90$6608f5b0$@nexbridge.com>
On Thu, Aug 01, 2024 at 02:03:31PM -0400, rsbecker@nexbridge.com wrote:
> 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:
Hmm. Script t7701 only has 8 sub-tests, but I think you're referring to
t7704.9
>
> 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
Interesting. Can you attach the full -vx output of this test, as well as
a ls -la from $GIT_DIR/objects/pack?
I suspect that this is a mtime resolution issue in whatever filesystem
is in use in your ia64 environment, but the full logs will help us
confirm that, or at least point is in a better direction.
Thanks in advance.
Thanks,
Taylor
next prev parent reply other threads:[~2024-08-01 19:23 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 [this message]
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=ZqvgmYl8BTYvsSa0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.