git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2
@ 2021-05-31 18:35 Randall S. Becker
  0 siblings, 0 replies; 3+ messages in thread
From: Randall S. Becker @ 2021-05-31 18:35 UTC (permalink / raw)
  To: git

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
packname_1=
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



-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2
@ 2021-06-01 14:51 Randall S. Becker
  0 siblings, 0 replies; 3+ messages in thread
From: Randall S. Becker @ 2021-06-01 14:51 UTC (permalink / raw)
  To: git

On May 31, 2021 2:36 PM, I wrote:
>To: 'git@vger.kernel.org' <git@vger.kernel.org>
>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
>packname_1=
>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
debug?

Thanks,
Randall


^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2
@ 2021-06-01 15:09 Randall S. Becker
  0 siblings, 0 replies; 3+ messages in thread
From: Randall S. Becker @ 2021-06-01 15:09 UTC (permalink / raw)
  To: git

On June 1, 2021 10:52 AM, I wrote:
>To: 'git@vger.kernel.org' <git@vger.kernel.org>
>Subject: RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2
>
>On May 31, 2021 2:36 PM, I wrote:
>>To: 'git@vger.kernel.org' <git@vger.kernel.org>
>>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
>>packname_1=
>>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
debug?

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?

Thanks,
Randall


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-06-01 15:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-01 14:51 [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2 Randall S. Becker
  -- strict thread matches above, loose matches on Subject: below --
2021-06-01 15:09 Randall S. Becker
2021-05-31 18:35 Randall S. Becker

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