mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <>
To: <>
Subject: RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2
Date: Tue, 1 Jun 2021 11:09:38 -0400	[thread overview]
Message-ID: <00c901d756f8$275a5ab0$760f1010$> (raw)

On June 1, 2021 10:52 AM, I wrote:
>To: '' <>
>Subject: RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2
>On May 31, 2021 2:36 PM, I wrote:
>>To: '' <>
>>Subject: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2
>>This one started at 2.32.0-rc1, AFIAK:
>>expecting success of 5300.2 'pack without delta':
>>        packname_1=$(git pack-objects --progress --window=0 test-1 \
>>                        <obj-list 2>stderr) &&
>>        check_deltas stderr = 0
>>+ + git pack-objects --progress --window=0 test-1
>>+ 0< obj-list 2> stderr
>>error: last command exited with $?=128
>>not ok 2 - pack without delta
>>#               packname_1=$(git pack-objects --progress --window=0
>>test-1 \ #                               <obj-list 2>stderr) && #
>>check_deltas stderr = 0 #
>>Stderr contains:
>>Enumerating objects: 8, done.
>>Counting objects: 100% (8/8), done.
>>fatal: fsync error on '.git/objects/pack/tmp_pack_Y6t3Br': Interrupted
>>system call
>I thought this was limited to the NonStop x86, but it also apples to NonStop ia64. Any wisdom on where this might be, so I can

This may be a recurrence of a MAX_SIZE problem from a few years ago with xread, xwrite. The I/Os that are failing appear to be using
using IO sizes larger than the platform maximum. This will cause fsync to fail with EINTR. Pointers on where this might be, please?


             reply	other threads:[~2021-06-01 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 15:09 Randall S. Becker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-01 14:51 [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2 Randall S. Becker
2021-05-31 18:35 Randall S. Becker

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:

  List information:

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

  git send-email \
    --in-reply-to='00c901d756f8$275a5ab0$760f1010$' \ \ \

* 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

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).