Re: [Lilypond-auto] Patchy report

[John Mandereau]

Il giorno mar, 09/10/2012 alle 09.57 +0200, David Kastrup ha scritto:
> John Mandereau <address@hidden> writes:
> 
> > Hi,
> >
> > I quote some of the logs below...
> > Il giorno mar, 09/10/2012 alle 00.33 +0000, address@hidden ha
> > scritto:
> >> 21:58:01 (UTC) Begin LilyPond compile, previous commit at  
> >> c7a3623a056891d48b13fe14fd6ee042ac666822
> >> 21:58:27 Merged staging, now at:   c7a3623a056891d48b13fe14fd6ee042ac666822
> >> 21:58:29   Success:                sudo -u lilybuild ./autogen.sh 
> >> --noconfigure
> >> 21:59:05   Success:                sudo -u lilybuild 
> >> /home/lilybuild/staging/configure --disable-optimising
> >> 21:59:15   Success:                sudo -u lilybuild nice make clean
> >> 22:16:12   Success:                sudo -u lilybuild nice make -j2 
> >> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> >> 22:38:05   Success:                sudo -u lilybuild nice make test -j2 
> >> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> >> 00:33:31 *** FAILED BUILD ***
> >>    sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> >>    Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb
> 
> That's several weeks ago.

Indeed, this is crazy, because you can see on lilypond-auto list that
Patchy successfully built the same Git committish
c7a3623a056891d48b13fe14fd6ee042ac666822 one day ago.


> indicates that it has not changed at all in the (considerable) time span
> involved.  Either your build system, your version of Patchy, or your
> hardware is broken.

This could be well a hardware problem (again).  The system administrator
of the MSHPN may propose a replacement computer this month or in
November.

John