On Jul 13, 2011, at 9:37 PM, Neil Puttock wrote: > On 13 July 2011 11:22, m...@apollinemike.com <m...@apollinemike.com> wrote: > >> You're right - they would have been the same. I think this error may have >> been introduced in a recent patch, in which case it is a regression. I'd >> have to run git-bisect to figure it out, though, but all of my CPU is being >> eaten up by audio rendering at the moment (and just months ago I was >> bragging about my fast computer...serves me right...). > > The cyclic redundancies were present with the initial commit which > added beam-skip.ly. > > As I noted on issue 1706, this regression test shows up every time I > do make check (it's become one of those annoying snippets which > switches behaviour between baseline and test).
Ok. Was I too narrow in my original fix? I can work on something cleaner to address the segfault that doesn't lead to cyclical dependencies so that this doesn't perturb future generations of regtests. Cheers, MS _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
