git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <rsbecker@nexbridge.com>
To: <rsbecker@nexbridge.com>, "'Git List'" <git@vger.kernel.org>
Subject: RE: [Bug] Test 1450.91 Fails on NonStop
Date: Wed, 15 Feb 2023 12:59:14 -0500	[thread overview]
Message-ID: <000101d94167$3a5f2090$af1d61b0$@nexbridge.com> (raw)
In-Reply-To: <000001d94165$3d1cf2f0$b756d8d0$@nexbridge.com>

On Wednesday, February 15, 2023 12:45 PM, I wrote:
>Test 1450.91 fails...
>
>I am not sure what is going on here other than test_must_fail is not
processing the
>completion code.  This was run on both NonStop platform variants with sh
and bash.
>The expected file contains what is expected.
>actual is empty. There are no very large files anywhere in the trash
directory.
>
>expecting success of 1450.91 'fsck error on gitattributes with excessive
>size':
>        blob=$(test-tool genzeros $((100 * 1024 * 1024 + 1)) | git
hash-object -w --stdin)
>&&
>        test_when_finished "remove_object $blob" &&
>        tree=$(printf "100644 blob %s\t%s\n" $blob .gitattributes | git
>mktree) &&
>        test_when_finished "remove_object $tree" &&
>        cat >expected <<-EOF &&
>        error in blob $blob: gitattributesLarge: .gitattributes too large
to parse
>        EOF
>        test_must_fail git fsck --no-dangling >actual 2>&1 &&
>        test_cmp expected actual
>
>+ + git hash-object -w --stdin
>+ test-tool genzeros 104857601
>blob=e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
>+ test_when_finished remove_object
>+ e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
>+ + git mktree
>+ printf 100644 blob %s\t%s\n e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
>.gitattributes
>tree=f8614bda784833ac9ab9e82c4ca296948c6ddd60
>+ test_when_finished remove_object
>+ f8614bda784833ac9ab9e82c4ca296948c6ddd60
>+ cat
>+ 1> expected 0<<
>error in blob e69de29bb2d1d6434b8b29ae775ad8c2e48c5391: gitattributesLarge:
>.gitattributes too large to parse
>+ test_must_fail git fsck --no-dangling
>+ 1> actual 2>& 1
>test_must_fail: command succeeded: git fsck --no-dangling
>error: last command exited with $?=1
>not ok 91 - fsck error on gitattributes with excessive size #
>#               blob=$(test-tool genzeros $((100 * 1024 * 1024 + 1)) | git
>hash-object -w --stdin) &&
>#               test_when_finished "remove_object $blob" &&
>#               tree=$(printf "100644 blob %s\t%s\n" $blob .gitattributes |
>git mktree) &&
>#               test_when_finished "remove_object $tree" &&
>#               cat >expected <<-EOF &&
>#               error in blob $blob: gitattributesLarge: .gitattributes too
>large to parse
>#               EOF
>#               test_must_fail git fsck --no-dangling >actual 2>&1 &&
>#               test_cmp expected actual
>#
>1..91
>J

This seems to have started at 2.39. I first noticed it 2.39.2.


  reply	other threads:[~2023-02-15 17:59 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 [this message]
2023-02-15 18:02 ` Jeff King
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='000101d94167$3a5f2090$af1d61b0$@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.
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).