RE: [BUG] Weird breakages in t1450 #2 on NonStop

2018-01-12 Thread Randall S. Becker
On January 12, 2018 9:39 AM, Jeff King wrote: > On Thu, Jan 11, 2018 at 04:39:04PM -0500, Randall S. Becker wrote: > > > > executed because the test_commit fails with a non-zero git commit > > > completion code. There is no rn (actual r n 252 252 252 252) in > > > the objects directory - even

Re: [BUG] Weird breakages in t1450 #2 on NonStop

2018-01-12 Thread Jeff King
On Thu, Jan 11, 2018 at 04:39:04PM -0500, Randall S. Becker wrote: > > executed because the test_commit fails with a non-zero git commit > > completion code. There is no rn (actual r n 252 252 252 252) in > > the objects directory - even the 'rn' does not correspond to > > anything.. I am susp

RE: [BUG] Weird breakages in t1450 #2 on NonStop

2018-01-11 Thread Randall S. Becker
On January 11, 2018 9:46 AM, I wrote: > This one has me scratching my head: > > The object file name being reported below in t1450, subtest 2 is corrupt, but I > can't figure out why the script might be generating this condition - there's > nothing apparent, but it looks like the git commit -m C s

[BUG] Weird breakages in t1450 #2 on NonStop

2018-01-11 Thread Randall S. Becker
This one has me scratching my head: The object file name being reported below in t1450, subtest 2 is corrupt, but I can't figure out why the script might be generating this condition - there's nothing apparent, but it looks like the git commit -m C step is reporting or using a bad name. This break