----- Original Message -----
From: "Phil Holmes" <m...@philholmes.net>
To: "Julien Rioux" <julien.ri...@gmail.com>
Cc: <re...@codereview-hr.appspotmail.com>; <lilypond-devel@gnu.org>
Sent: Wednesday, January 11, 2012 9:52 PM
Subject: Re: Build translated manuals: Don't rebuild everything
eachtimeunless necessary. (issue 5494069)
----- Original Message -----
From: "Julien Rioux" <julien.ri...@gmail.com>
To: "Phil Holmes" <m...@philholmes.net>
Cc: <lilypond-devel@gnu.org>; <re...@codereview-hr.appspotmail.com>
Sent: Wednesday, January 11, 2012 9:41 PM
Subject: Re: Build translated manuals: Don't rebuild everything each
timeunless necessary. (issue 5494069)
On Wed, Jan 11, 2012 at 1:50 PM, Phil Holmes <m...@philholmes.net> wrote:
----- Original Message ----- From: <julien.ri...@gmail.com>
To: <julien.ri...@gmail.com>
Cc: <re...@codereview-hr.appspotmail.com>; <lilypond-devel@gnu.org>
Sent: Wednesday, January 11, 2012 2:39 PM
Subject: Re: Build translated manuals: Don't rebuild everything each
timeunless necessary. (issue 5494069)
Please review. I tested make, make check, make doc, and do not get any
problem. However, with the previous versions I also did not get any
problem, yet I broke staging. I would be grateful if someone with a fast
machine could test a parallel make doc. I would not be comfortable
pushing to staging without this test.
Regards,
Julien
On my fast system, make doc takes 12min 30 approx and currently produces
a
6.5 meg logfile. I've run a system patched with this, and it ran for over
20 minutes, with no apparent updates to the output, which was "only"
about 1
meg. Only one CPU was being used (of 8) and this was 100% processing
make.
make output is available if you want to see what I have.
--
Phil Holmes
Thanks for testing. Did make doc ever finish? Maybe it decided that
things need to be done in series, which could take up to 1h40m based
on your fast parallel build on 8 CPUs. You can send the output
privately.
Thanks,
Regards,
Julien
================================================
I terminated it before it got that far. I'll run it again tomorrow to
see.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Let it run for almost 4 hours tonight. It produces output for about 12
minutes and then takes a single CPU for 100% load, with no console output.
I've zipped the 1 meg output file and sent it to Julien off-list. This is
with a core i7 - 4 processor hyperthreaded - running as make -j9
CPU_COUNT=9.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
