Il giorno mar, 28/08/2012 alle 19.00 +0100, Phil Holmes ha scritto: > ----- Original Message ----- > From: <grenoui...@lilynet.net> > To: <lilypond-a...@gnu.org> > Cc: <lilypond-devel@gnu.org> > Sent: Tuesday, August 28, 2012 5:39 PM > Subject: Patchy report > > > > 13:58:03 (UTC) Begin LilyPond compile, previous commit at > > e6073c719af153e80ba9f31ed96040a3782a180a > > 13:58:11 Another instance (PID 29635) is already running. > > 14:28:18 Another instance (PID 29635) is already running. > > 14:58:26 Another instance (PID 29635) is already running. > > 15:29:06 Merged staging, now at: e6073c719af153e80ba9f31ed96040a3782a180a > > 15:29:09 Success: sudo -u lilybuild ./autogen.sh --noconfigure > > 15:29:49 Success: sudo -u lilybuild > > /home/lilybuild/staging/configure --disable-optimising > > 15:29:59 Success: sudo -u lilybuild nice make clean > > 15:45:29 Success: sudo -u lilybuild nice make -j2 CPU_COUNT=2 > > ANTI_ALIAS_FACTOR=1 > > 16:07:21 Success: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 > > ANTI_ALIAS_FACTOR=1 > > 16:39:54 *** FAILED BUILD *** > > sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1 > > Previous good commit: 30f457de4178d3e049336aaf50afe17b3b3a1135 > > Current broken commit: e6073c719af153e80ba9f31ed96040a3782a180a > > Don't know what the problem was, but I ran test-patchy-staging to find out, > and all was well. As of now, master==staging.
When I read that message, the log had already been overwritten by next Patchy run, but from the timestamps it might well be a crash of LilyPond in doc build caused by some hardware memory inconsistency: this month Grenouille have encountered at least two GCC segfaults, one or two segfaults, some weird typechecking error, an almost uncountable number of "parsed objects should be dead" warnings... I'll see with Mike and the MSH admin what we can do, I hope we can find a solution without buying much or any hardware (making Grenouille run with only one of the two 1 GB RAM devices, getting in donation a second-hand but well-running computer suitable as a server possibly putting just a new hard disk on it...), as I think LilyPond users and developers would preferably spend money in funding development by humans. Best, John _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
