lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Failed make doc for Patchy


From: David Kastrup
Subject: Re: Failed make doc for Patchy
Date: Wed, 14 Mar 2012 20:16:17 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux)

James <address@hidden> writes:

> I am not at home but Patchy complained just now.
>
>
> ---------- Forwarded message ----------
> From:  <address@hidden>
> Date: 14 March 2012 18:34
> Subject: Patchy email
>
>
>
> Merged staging, now at: c6a925ecd742196979038804b02846faad7f2cc9
>
>        Success:                ./autogen.sh --noconfigure
>
>        Success:                ../configure --disable-optimising
>
>        Success:                nice make clean -j6 CPU_COUNT=6
>
>        Success:                nice make -j6 CPU_COUNT=6
>
>        Success:                nice make test -j6 CPU_COUNT=6
>
> *** FAILED BUILD ***
>
>        nice make doc -j6 CPU_COUNT=6
>
>        Previous good commit:   d11dbf277719c0179c5520154c925839d969a535
>
>        Current broken commit:  c6a925ecd742196979038804b02846faad7f2cc9


Documentation has not been touched between master and staging.  A change
by Carl would have triggered more likely in "make test" than in "make
doc".  That makes changes from me (or a Heisenbug) most likely.

My personal suspect would have been

commit 65c8ce914c62117fb61a21237f7dcf80ebb0cc6e
Author: David Kastrup <address@hidden>
Date:   Sun Mar 11 12:16:52 2012 +0100

    Make Score an initial Timing alias to allow for context mods


But then I am pretty certain that I actually ran "make info" on that one
to make reasonably sure it did not cause offense.

I am taking a look right now.  If you have relevant log file data, it
might speed things up.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]