On Sat, Dec 12, 2009 at 7:45 AM, Joe Neeman <joenee...@gmail.com> wrote:
> On Sat, 2009-12-12 at 07:00 +0000, Graham Percival wrote:
>> To assist in this, in the near future I'll set up a daily out-of-tree
>> building system for lilypond (I've done it before for marsyas).  If
>> any build fails, it will send rude messages to lilypond-devel with a
>> list of the names of everybody who committed things since the last
>> successful build.  :)
>
> Would it be feasible (using git-bisect) to pin down the exact failing
> commit?

Not worth it, IMO.
1)  each build needs to start from clean
2)  The main code can be done with -j4 so it's finished in 10-15
minutes, but building the docs (under the best circumstances) can only
be done reliably with -j1, so it takes 2 hours or something like that.
3)  we don't screw around with the build system all that much... and
when somebody *does* change anything, they should check that it
worked.  I didn't realize how much more finicky the out-of-tree build
was, but as long as we make it clear that any build-system
modifications should be tested with a clean out-of-tree build, I think
it's fine.

Narrowing it down to a 24-hour period should be enough to catch the
unintentional breakages.

Cheers,
- Graham


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to