git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Todd Zullinger <tmz@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	git <git@vger.kernel.org>, Derrick Stolee <stolee@gmail.com>
Subject: Re: Testsuite failure on s390x and sparc64 after 6840fe9ee2
Date: Mon, 31 Mar 2025 11:48:56 -0400	[thread overview]
Message-ID: <Z-q5aOIahoUKSyBi@teonanacatl.net> (raw)
In-Reply-To: <Z-qKGqpbdaW9WCrP@pks.im>

[cc: fixed Derrick's address]

Hi Patrick,

Patrick Steinhardt wrote:
> Thanks for the additional information!

Thank you for looking into it and providing a patch!

> One thing I stumbled over: the `--min-batch-size` parameter is parsed
> using `OPT_INTEGER()`, which expects the value pointer to point to an
> integer. But we pass `struct backfill_context::min_batch_size`, which is
> of type `size_t`. Maybe that's causing us to end up with an invalid
> value?
> 
> Could you please check whether the below diff fixes the issue for you?
> If so I can turn it into a proper patch.

It does indeed lead to a successful test run:

t5620-backfill.sh ..................................
ok 1 - setup repo for object creation
ok 2 - setup bare clone for server
ok 3 - do partial clone 1, backfill gets all objects
ok 4 - do partial clone 2, backfill min batch size
ok 5 - backfill --sparse without sparse-checkout fails
ok 6 - backfill --sparse
ok 7 - backfill --sparse without cone mode (positive)
ok 8 - backfill --sparse without cone mode (negative)
ok 9 - create a partial clone over HTTP
ok 10 - backfilling over HTTP succeeds
# passed all 10 test(s)
1..10

Source: https://kojipkgs.fedoraproject.org//work/tasks/3947/130943947/build.log

I tested it against the other common architectures the
Fedora build system provides as well, to be sure no others
regressed, although there aren't as many as the Debian build
system :).

-- 
Todd

  reply	other threads:[~2025-03-31 15:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 20:42 Testsuite failure on s390x and sparc64 after 6840fe9ee2 John Paul Adrian Glaubitz
2025-03-26 22:27 ` Todd Zullinger
2025-03-28  9:29   ` Patrick Steinhardt
2025-03-28  9:30     ` Patrick Steinhardt
2025-03-28  9:38     ` John Paul Adrian Glaubitz
2025-03-28 14:08       ` Todd Zullinger
2025-03-28 15:37         ` Todd Zullinger
2025-03-31 12:27           ` Patrick Steinhardt
2025-03-31 15:48             ` Todd Zullinger [this message]
2025-03-31 18:17             ` SZEDER Gábor
2025-04-01  2:33               ` Jeff King
2025-04-01  3:10                 ` Jeff King
2025-04-01 11:43                   ` Patrick Steinhardt
2025-04-01 15:04                     ` Patrick Steinhardt

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=Z-q5aOIahoUKSyBi@teonanacatl.net \
    --to=tmz@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=ps@pks.im \
    --cc=stolee@gmail.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).