Re: t5400 failure on Windows

2017-05-17 Thread Johannes Sixt
Am 17.05.2017 um 07:44 schrieb Jeff King: > I wonder if there's a way we could convince the trace for the two > programs to go to separate locations. We don't care about receive-pack's > trace at all. So maybe: This works. Below it is with a commit message. I'm unsure about the sign-off procedure,

Re: t5400 failure on Windows

2017-05-16 Thread Jeff King
On Tue, May 16, 2017 at 08:35:46PM +0200, Johannes Sixt wrote: > Am 16.05.2017 um 00:24 schrieb Jeff King: > >4. There is something racy and unportable about both programs writing > > to the same trace file. It's opened with O_APPEND, which means that > > each write should atomical

Re: t5400 failure on Windows

2017-05-16 Thread Johannes Sixt
Am 16.05.2017 um 00:24 schrieb Jeff King: 4. There is something racy and unportable about both programs writing to the same trace file. It's opened with O_APPEND, which means that each write should atomically position the pointer at the end of the file. Is it possible there's

Re: t5400 failure on Windows

2017-05-15 Thread Jeff King
On Mon, May 15, 2017 at 10:05:29PM +0200, Johannes Sixt wrote: > I observe the following failure on Windws with origin/next, in > t5400-send-pack.sh > > +++ diff -u expect refs > --- expect Mon May 15 06:54:59 2017 > +++ refsMon May 15 06:54:59 2017 > @@ -1,4 +1,3 @@ > 5285e1710002a

t5400 failure on Windows

2017-05-15 Thread Johannes Sixt
I observe the following failure on Windws with origin/next, in t5400-send-pack.sh +++ diff -u expect refs --- expect Mon May 15 06:54:59 2017 +++ refsMon May 15 06:54:59 2017 @@ -1,4 +1,3 @@ 5285e1710002a06a379056b0d21357a999f3c642 refs/heads/master -5285e1710002a06a379056b0d21357a99