Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-09-27 Thread lilypond
Updates: Status: Verified Comment #11 on issue 1529 by brownian.box: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 (No comment was entered for this change.) ___

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-09-15 Thread lilypond
Comment #9 on issue 1529 by reinhold...@gmail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 I just did a test run with current master, changed two snippets and ran make check... Result is attached. As you can see,

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-09-15 Thread lilypond
Updates: Labels: -Priority-Low Comment #10 on issue 1529 by percival.music.ca: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 hmm. Most of the spam in the regtest comparison is not because of an actually-changed

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-09-11 Thread lilypond
Comment #8 on issue 1529 by philehol...@googlemail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 Looking at the output for the 2.15.10 regtests (there's quite a bit to scroll down...) I still see the

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-09-01 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_15_10 Comment #6 on issue 1529 by reinhold...@gmail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 Pushed as commit a3c1eedb175600c8623d423dca01c35e80c7df9b

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-09-01 Thread lilypond
Comment #7 on issue 1529 by reinhold...@gmail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 Had to rebase before pushing, new id is 4ccfb61ecfa8b32f8c5d87e75c569171bbc54ba6

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-08-27 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #5 on issue 1529 by pkx1...@gmail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 Passes Make and reg tests ___

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-08-24 Thread lilypond
Updates: Labels: -Patch-new Patch-needs_work Comment #3 on issue 1529 by pkx1...@gmail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 passes make but reg test check fails --snip-- reading

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-08-15 Thread lilypond
Updates: Status: Started Owner: reinhold...@gmail.com Labels: Patch-new Comment #1 on issue 1529 by reinhold...@gmail.com: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 Patch is up for review:

Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

2011-02-20 Thread lilypond
Status: Accepted Owner: Labels: Type-Build Priority-Low Maintainability New issue 1529 by percival.music.ca: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 The regtest comparison looks at the console output of lilypond,