lilypond-a...@mandereau.net writes: > 10:35:12 (UTC) Begin LilyPond compile, previous commit at > d459b17897c0218450bfb0bab6403c16705bd17a > > 10:35:14 Merged staging, now at: > 65c53165ab3535a9186f501c9a8b454d07c82642 > > 10:35:17 Success: ./autogen.sh --noconfigure > > 10:35:50 Success: ../configure --disable-optimising > > 10:36:10 Success: nice make clean -j2 CPU_COUNT=2 > > 10:43:31 Success: nice make -j2 CPU_COUNT=2 > > 11:02:56 Success: nice make test -j2 CPU_COUNT=2 > > 11:58:21 *** FAILED BUILD *** > > nice make doc -j2 CPU_COUNT=2 > > Previous good commit: d459b17897c0218450bfb0bab6403c16705bd17a > > Current broken commit: 65c53165ab3535a9186f501c9a8b454d07c82642 > > 11:58:21 *** FAILED STEP *** > > merge from staging > > Failed runner: nice make doc -j2 CPU_COUNT=2 > > See the log file log-staging-nice-make-doc--j2-CPU_COUNT=2.txt
Since it is the same problem as we had previously from John's test run, it may make sense to wait whether this is also the opinion of another Patchy. If it is, we'd need to back this out. One thing that occured to me is that this contains a whole lot of public functions without any DOC string. No idea whether this might cause a problem for the documentation run, but it certainly is not much of a help for humans understanding the code. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
