----- Original Message -----
From: "Graham Percival" <gra...@percival-music.ca>
To: <lilypond.patchy.gra...@gmail.com>
Cc: <lilypond-devel@gnu.org>
Sent: Monday, January 09, 2012 8:22 AM
Subject: Re: Patchy email
On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
*** FAILED BUILD ***
nice make doc -j3 CPU_COUNT=3
Previous good commit: 820c7ff5d380e8ca52057717ab3176b5e40107fd
Current broken commit: 42984d05239a3c3be1ea859ba5214ce140448afc
The error message from this is the same as we had on jan 7:
---------------
Error ignored by lilylib
lilypond-book.py (GNU LilyPond) 2.15.25
Error trapped by lilypond-book
Please see
/main/large-tmp/lilypond-autobuild/build/out/lybook-db/snippet-names-1740910883.log
---------------
when that file only contains:
---------------
GNU LilyPond 2.15.25
Forking into jobs: (18440 18439 18438)
job 2 terminated with signal: 11
fatal error: Children (2) exited with errors.
-------------
I'm beginning to suspect that we have a random build failure,
rather than an actual problem in staging right now (or even on Jan
7). This is the only case where I haven't seen any info in the
logs.
- Graham
You get that forking (I believe) because of the CPU_COUNT setting. If it's
a reproducible error, it might be easier to find if you lose that setting
temporarily. Please feel free to raise an issue saying the log file is not
helpful in this case.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
