git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: rsbecker@nexbridge.com
Cc: 'Git List' <git@vger.kernel.org>
Subject: Re: [Bug] Test 1450.91 Fails on NonStop
Date: Wed, 15 Feb 2023 13:02:10 -0500	[thread overview]
Message-ID: <Y+0eIlsIxRr+1RYp@coredump.intra.peff.net> (raw)
In-Reply-To: <000001d94165$3d1cf2f0$b756d8d0$@nexbridge.com>

On Wed, Feb 15, 2023 at 12:44:59PM -0500, rsbecker@nexbridge.com wrote:

> + + git hash-object -w --stdin
> + test-tool genzeros 104857601
> blob=e69de29bb2d1d6434b8b29ae775ad8c2e48c5391

That's not right. e69de29bb is the empty blob. A hundred megabytes (plus
one) of zeroes should be d748d1b68b9dc69c4717ebc070dbc547d129bcc6.

So that is the root of your problem (the empty file will obviously not
trigger the "too large" fsck check), but I don't know why it would be
failing.

Maybe check the output of "test-tool genzeros 104857601" to make sure
that it as expected? If not, then the bug is somewhere in
t/helper/test-genzeros.c.

It's on the left-hand side of pipe. Maybe it is getting a write() error,
but we are ignoring it? Maybe a patch like this would help diagnose:

diff --git a/t/helper/test-genzeros.c b/t/helper/test-genzeros.c
index 8ca988d621..0574917005 100644
--- a/t/helper/test-genzeros.c
+++ b/t/helper/test-genzeros.c
@@ -18,14 +18,14 @@ int cmd__genzeros(int argc, const char **argv)
 	/* Writing out individual NUL bytes is slow... */
 	while (count < 0)
 		if (write(1, zeros, ARRAY_SIZE(zeros)) < 0)
-			return -1;
+			die_errno("write()");
 
 	while (count > 0) {
 		n = write(1, zeros, count < ARRAY_SIZE(zeros) ?
 			  count : ARRAY_SIZE(zeros));
 
 		if (n < 0)
-			return -1;
+			die_errno("write()");
 
 		count -= n;
 	}

-Peff

  parent reply	other threads:[~2023-02-15 18:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 17:44 [Bug] Test 1450.91 Fails on NonStop rsbecker
2023-02-15 17:59 ` rsbecker
2023-02-15 18:02 ` Jeff King [this message]
2023-02-15 18:49   ` rsbecker
2023-02-15 19:10     ` Junio C Hamano
2023-02-15 19:41       ` rsbecker
2023-02-15 19:59       ` Jeff King
2023-02-16  1:45         ` Junio C Hamano
2023-02-16  2:56           ` [PATCH] test-genzeros: avoid raw write(2) Junio C Hamano
2023-02-16  4:34             ` Jeff King
2023-02-16 16:09               ` Junio C Hamano
2023-02-16 16:14                 ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y+0eIlsIxRr+1RYp@coredump.intra.peff.net \
    --to=peff@peff.net \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).