Re: Continous Integration (was: RE: Git v2.13.1 SHA1 very broken)

Hi Adam, On Sun, 2 Jul 2017, Adam Dinwoodie wrote: > I do the builds for the Cygwin distribution on my normal PC (so > reasonably powerful but definitely not devoted to the purpose), and > doing the build and running the default tests takes in the region of 8 > hours for the 64-bit build and 12

Re: Continous Integration (was: RE: Git v2.13.1 SHA1 very broken)

On Tue, Jun 06, 2017 at 05:04:32PM +0200, Lars Schneider wrote: > > On 06 Jun 2017, at 16:47, Jason Pyeron wrote: > > > > Do we have Jenkins (or something else) setup for Git? > > > > We would be happy to donate (slave) VMs for cygwin builds og Git. > > > > -Jason Pyeron >

Re: Continous Integration (was: RE: Git v2.13.1 SHA1 very broken)

> On 06 Jun 2017, at 16:47, Jason Pyeron wrote: > > Do we have Jenkins (or something else) setup for Git? > > We would be happy to donate (slave) VMs for cygwin builds og Git. > > -Jason Pyeron > We use TravisCI for Linux, Mac, and (in a special way) Windows:

Continous Integration (was: RE: Git v2.13.1 SHA1 very broken)

Do we have Jenkins (or something else) setup for Git? We would be happy to donate (slave) VMs for cygwin builds og Git. -Jason Pyeron

Re: Git v2.13.1 SHA1 very broken

One could have configure ask some existing dependency that has already determined the byte order. For example: # perl -e 'use Config; $o=$Config{byteorder}; print(($o=~/^1234/ ? "little" : ($o=~/4321$/ ? "big" : "weird")), "\n");' little Good: less #ifdef soup; bad: not so great for

Re: Git v2.13.1 SHA1 very broken

On Tue, Jun 06, 2017 at 08:55:04PM +0900, Junio C Hamano wrote: > Adam Dinwoodie writes: > > > Digging briefly into the endianness detection, it appears Cygwin has > > both _LITTLE_ENDIAN and _BIG_ENDIAN defined. Git's detection works by > > assuming it's in a little endian

Re: Git v2.13.1 SHA1 very broken

Adam Dinwoodie writes: > Digging briefly into the endianness detection, it appears Cygwin has > both _LITTLE_ENDIAN and _BIG_ENDIAN defined. Git's detection works by > assuming it's in a little endian environment and switching to big endian > if it detects any of the defines

Re: Git v2.13.1 SHA1 very broken

On Tue, Jun 06, 2017 at 10:20:45AM +0900, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason writes: > > > That looks scary, can you please comment out this: > > > > #define SHA1DC_ALLOW_UNALIGNED_ACCESS > > > > In sha1dc/sha1.c and see if that helps, alternatively comment out

Re: Git v2.13.1 SHA1 very broken

Ævar Arnfjörð Bjarmason writes: > That looks scary, can you please comment out this: > > #define SHA1DC_ALLOW_UNALIGNED_ACCESS > > In sha1dc/sha1.c and see if that helps, alternatively comment out the > ifdefs guarded by "#ifdef _MSC_VER" calls in sha1dc/sha1.c That is

Re: Git v2.13.1 SHA1 very broken

On 06/06/17 00:20, Ramsay Jones wrote: > > > On 05/06/17 22:05, Ævar Arnfjörð Bjarmason wrote: >> On Mon, Jun 5, 2017 at 10:34 PM, Adam Dinwoodie wrote: >>> I'm trying to compile Git v2.13.1 to release for Cygwin, but it appears >>> a010391 ("sha1dc: update from upstream",

Re: Git v2.13.1 SHA1 very broken

On 05/06/17 22:05, Ævar Arnfjörð Bjarmason wrote: > On Mon, Jun 5, 2017 at 10:34 PM, Adam Dinwoodie wrote: >> I'm trying to compile Git v2.13.1 to release for Cygwin, but it appears >> a010391 ("sha1dc: update from upstream", 2017-05-20) is breaking a very >> significant

Re: Git v2.13.1 SHA1 very broken

On Mon, Jun 5, 2017 at 10:34 PM, Adam Dinwoodie wrote: > I'm trying to compile Git v2.13.1 to release for Cygwin, but it appears > a010391 ("sha1dc: update from upstream", 2017-05-20) is breaking a very > significant number of test cases in both 32-bit and 64-bit Cygwin >

Git v2.13.1 SHA1 very broken

I'm trying to compile Git v2.13.1 to release for Cygwin, but it appears a010391 ("sha1dc: update from upstream", 2017-05-20) is breaking a very significant number of test cases in both 32-bit and 64-bit Cygwin builds. The first failure is t.46 "validate object ID of a known tree"; output with