git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 20:58:41 -0400	[thread overview]
Message-ID: <ZqwvQUAqVozGHG/t@nand.local> (raw)
In-Reply-To: <032201dae461$c7bcc9d0$57365d70$@nexbridge.com>

On Thu, Aug 01, 2024 at 06:25:51PM -0400, rsbecker@nexbridge.com wrote:
> ls output with second resolution is here - the file system does not have nanosecond resolution despite showing zeros:
>
> /home/ituglib/randall/git/t/trash directory.t7704-repack-cruft/max-cruft-size-prune/.git/objects/pack: ls -la --full-time
> total 11
> drwxrwxrwx 1 ITUGLIB.RANDALL ITUGLIB 4096 2024-08-01 16:18:55.000000000 -0600 .
> drwxrwxrwx 1 ITUGLIB.RANDALL ITUGLIB 4096 2024-08-01 16:18:48.000000000 -0600 ..
> -r--r--r-- 1 ITUGLIB.RANDALL ITUGLIB 1156 2024-08-01 16:18:52.000000000 -0600 pack-68c6c8c8538900694c32380ac1484201c8b60d8d.idx
> -r--r--r-- 1 ITUGLIB.RANDALL ITUGLIB  217 2024-08-01 16:18:52.000000000 -0600 pack-68c6c8c8538900694c32380ac1484201c8b60d8d.pack
> -r--r--r-- 1 ITUGLIB.RANDALL ITUGLIB   64 2024-08-01 16:18:52.000000000 -0600 pack-68c6c8c8538900694c32380ac1484201c8b60d8d.rev

Ah, I suspect that this is even less interesting than imprecise mtime
resolution. The test expects that the packs are larger than 1M so that
we can exercise writing multiple cruft packs as part of the setup.

But that pack is only 217 bytes, which wouldn't trigger the split. I'm
suspicious that it's even packing the cruft objects at all, so I'm
curious if you can find $foo, $bar, and $baz in the cruft pack's .idx
file(s, if multiple) after the first 'git repack -d --cruft'.

Assuming they are there, it's possible that setting repack.cruftWindow
in the test repository would do the trick.

But I'm suspicious that that's even what's going on since
generate_random_blob()'s first argument is a seed, and all three objects
have different seeds, so I don't think they would even be considered
good delta candidates for one another. But it's also possible that your
generate_random_blob() behaves differently from my own.

Thanks,
Taylor

  reply	other threads:[~2024-08-02  0:58 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 [this message]
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=ZqwvQUAqVozGHG/t@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).