John, On 14 May 2012 12:52, <john.mander...@gmail.com> wrote: > Begin LilyPond compile, commit: c597a126f11943be74a98efee056ab54ae729315 > > Merged staging, now at: c597a126f11943be74a98efee056ab54ae729315 > > Success: ./autogen.sh --noconfigure > > Success: ../configure --disable-optimising > > Success: nice make clean CPU_COUNT=3 > > Success: nice make CPU_COUNT=3 > > Success: nice make test CPU_COUNT=3 > > *** FAILED BUILD *** > > nice make doc CPU_COUNT=3 > > Previous good commit: > > Current broken commit: c597a126f11943be74a98efee056ab54ae729315 > >
As my machine is running this merge in parallel with yours (I cannot access it from work so it remains on for another run at around 18:00 BST) you can still test it works. The best way is to remove the 'last commit' ID and make it blank, then re-run the script, even if there is nothing to merge it will still do a full compile (I think) and that will tell you it is working. I don't know the ramifications of running two merges at the same time so if you can keep it an hour either side of 18:00 BST to NOT compile we won't hit each other. James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
