On Jan 9, 2012, at 10:18 AM, Graham Percival wrote: > On Mon, Jan 09, 2012 at 08:22:50AM +0000, Graham Percival wrote: >> 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 >> >> 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. > > A new staging build just succeeded. It's just possible that > Mike's fix 5e4ca89 solved it, or it could be sheer random fluke. > This is not a happy situation. >
My guy says random fluke - if ghostscript had caused the failure in the previous build, there would have been the ghostscript stack trace in the log files :( Cheers, MS _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
