{"thread":{"id":"55820","subject":"RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2","startedAt":"2021-06-01T15:09:47Z","lastAt":"2021-06-01T15:09:47Z","messageCount":1,"participants":["Randall S. Becker"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"426142","messageId":"00c901d756f8$275a5ab0$760f1010$@nexbridge.com","threadId":"55820","inReplyTo":null,"subject":"RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2","fromName":"Randall S. Becker","fromEmail":"rsbecker@nexbridge.com","sentAt":"2021-06-01T15:09:38Z","receivedAt":"2021-06-01T15:09:47Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On June 1, 2021 10:52 AM, I wrote:\n>To: 'git@vger.kernel.org' <git@vger.kernel.org>\n>Subject: RE: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2\n>\n>On May 31, 2021 2:36 PM, I wrote:\n>>To: 'git@vger.kernel.org' <git@vger.kernel.org>\n>>Subject: [BUG] t5300 fails tests on NonStop x86 at 2.32.0-rc2\n>>\n>>This one started at 2.32.0-rc1, AFIAK:\n>>\n>>expecting success of 5300.2 'pack without delta':\n>>        packname_1=$(git pack-objects --progress --window=0 test-1 \\\n>>                        <obj-list 2>stderr) &&\n>>        check_deltas stderr = 0\n>>\n>>+ + git pack-objects --progress --window=0 test-1\n>>+ 0< obj-list 2> stderr\n>>packname_1=\n>>error: last command exited with $?=128\n>>not ok 2 - pack without delta\n>>#\n>>#               packname_1=$(git pack-objects --progress --window=0\n>>test-1 \\ #                               <obj-list 2>stderr) && #\n>>check_deltas stderr = 0 #\n>>\n>>Stderr contains:\n>>\n>>Enumerating objects: 8, done.\n>>Counting objects: 100% (8/8), done.\n>>fatal: fsync error on '.git/objects/pack/tmp_pack_Y6t3Br': Interrupted\n>>system call\n>\n>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\ndebug?\n\nThis 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\nusing IO sizes larger than the platform maximum. This will cause fsync to fail with EINTR. Pointers on where this might be, please?\n\nThanks,\nRandall\n\n"}]}