Re: Patchy report

[David Kastrup]

John Mandereau <address@hidden> writes:

> Il giorno ven, 31/08/2012 alle 00.38 +0200, David Kastrup ha scritto:
>> address@hidden writes:
>> 
>> > 21:58:01 (UTC) Begin LilyPond compile, previous commit at  
>> > e15e0d22810063b79da891bbf472ecc39d09c02c
>> > 21:58:15 From git.savannah.gnu.org:/srv/git/lilypond
>> >    5d2bd06..e15e0d2  master     -> master
>> >    201be86..e593c62  translation -> translation
>> > 21:58:59 Merged staging, now at:   e15e0d22810063b79da891bbf472ecc39d09c02c
>> > 21:59:01   Success:                sudo -u lilybuild ./autogen.sh 
>> > --noconfigure
>> > 21:59:37   Success:                sudo -u lilybuild 
>> > /home/lilybuild/staging/configure --disable-optimising
>> > 21:59:47   Success:                sudo -u lilybuild nice make clean
>> > 22:00:30 *** FAILED BUILD ***
>> >    sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>> >    Previous good commit:   66a7c3e925cbc1a34eaad04f80d4bc42ad9834ac
>> >    Current broken commit:  e15e0d22810063b79da891bbf472ecc39d09c02c
>> > 22:00:30 *** FAILED STEP ***
>> >    merge from staging
>> >    Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
>> > ANTI_ALIAS_FACTOR=1
>> > See the log file 
>> > log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
>> > 22:00:31 Traceback (most recent call last):
>> >   File
>> > "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init_
>
> This is a GCC segfault with GCC 4.4.7-2 (Debian unstable).  On the
> contrary, the crash of "make doc" this morning on translation branch
> comes from an error in the Czech doc Texinfo source.
>
>
>> Grenouille currently seems to be wrong too often to be useful.  Do you
>> have a way of checking the integrity of its RAM?
>
> I contacted the administrator for checking this, if I need to be
> physically present there we won't be able to check this before Monday.

Some of the recent reports from Grenouille actually might suggest that
it might be testing against an unrelated test-baseline.  Perhaps you are
taking wrong shortcuts, or are mixing up in-place and out-of-place
builds or storing your test-baseline in a different place you read it
from again?

-- 
David Kastrup