git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: [Bug] Test 1450.91 Fails on NonStop

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Feb 15, 2023, 17:59 UTC
Message-ID
<000101d94167$3a5f2090$af1d61b0$@nexbridge.com>
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)
Show 7 quoted lines
>&&
>        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
Show 39 quoted lines
>        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.
Previous: rsbecker@nexbridge.comNext: Jeff King
Message 2 of 12 in “[Bug] Test 1450.91 Fails on NonStop”
  1. rsbecker@nexbridge.comFeb 15, 2023
  2. rsbecker@nexbridge.comFeb 15, 2023
  3. Jeff KingFeb 15, 2023
  4. rsbecker@nexbridge.comFeb 15, 2023
  5. Junio C HamanoFeb 15, 2023
  6. rsbecker@nexbridge.comFeb 15, 2023
  7. Jeff KingFeb 15, 2023
  8. Junio C HamanoFeb 16, 2023
  9. test-genzeros: avoid raw write(2)Junio C Hamano, Feb 16, 2023
  10. Jeff KingFeb 16, 2023
  11. Junio C HamanoFeb 16, 2023
  12. rsbecker@nexbridge.comFeb 16, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.