PATCHES: Countdown for September 28th
Hello, Here is the current patch countdown list. The next countdown will be on October 1st A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ __ Push: 4972 Chord repetition erroneously tagged - David Kastrup https://sourceforge.net/p/testlilyissues/issues/4972 http://codereview.appspot.com/303570043 4969 Update texinfo.tex from upstream - Masamichi Hosoda https://sourceforge.net/p/testlilyissues/issues/4969 http://codereview.appspot.com/310220043 Countdown: 4977 Doc: update toplevel-score-handler definition reference - Paul Morris https://sourceforge.net/p/testlilyissues/issues/4977 http://codereview.appspot.com/308490043 Review: 4937 [GSoC] Implement cross-voice dynamic spanners - Nathan Chou https://sourceforge.net/p/testlilyissues/issues/4937 http://codereview.appspot.com/304160043 New: No new patches at this time. Waiting 4600 Let notes/rests suppress multi-measure rest grobs - Dan Eble https://sourceforge.net/p/testlilyissues/issues/4600 http://codereview.appspot.com/265160043 Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patchy email
07:29:54 (UTC) Begin LilyPond compile, previous commit at
8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:58 Merged staging, now at:8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:59Success:./autogen.sh --noconfigure
07:30:16Success:/tmp/lilypond-autobuild/configure
--enable-checking
07:30:18Success:nice make clean
07:40:20Success:nice make -j3 CPU_COUNT=3
07:50:03Success:nice make test -j3 CPU_COUNT=3
08:54:44Success:nice make doc -j3 CPU_COUNT=3
08:56:12 *** FAILED STEP ***
merge from staging
Command '['git', 'fetch']' returned non-zero exit status 128
ssh: Could not resolve hostname git.sv.gnu.org: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
08:56:12 Traceback (most recent call last):
File
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line
530, in handle_staging
self.merge_push ()
File
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line
469, in merge_push
run ("git fetch")
File
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line
105, in run
raise FailedCommand ("Command '%s' returned non-zero exit status %d\n%s" %
(cmd, returncode, stderr.strip ()))
FailedCommand: Command '['git', 'fetch']' returned non-zero exit status 128
ssh: Could not resolve hostname git.sv.gnu.org: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
pat...@gnu.org writes:
> 07:29:54 (UTC) Begin LilyPond compile, previous commit at
> 8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
> 07:29:58 Merged staging, now at: 8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
> 07:29:59 Success:./autogen.sh --noconfigure
> 07:30:16 Success:/tmp/lilypond-autobuild/configure
> --enable-checking
> 07:30:18 Success:nice make clean
> 07:40:20 Success:nice make -j3 CPU_COUNT=3
> 07:50:03 Success:nice make test -j3 CPU_COUNT=3
> 08:54:44 Success:nice make doc -j3 CPU_COUNT=3
> 08:56:12 *** FAILED STEP ***
> merge from staging
> Command '['git', 'fetch']' returned non-zero exit status 128
> ssh: Could not resolve hostname git.sv.gnu.org: Name or service not known
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> 08:56:12 Traceback (most recent call last):
> File
> "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py",
> line 530, in handle_staging
> self.merge_push ()
> File
> "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py",
> line 469, in merge_push
> run ("git fetch")
> File
> "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py",
> line 105, in run
> raise FailedCommand ("Command '%s' returned non-zero exit status %d\n%s"
> % (cmd, returncode, stderr.strip ()))
> FailedCommand: Command '['git', 'fetch']' returned non-zero exit status 128
> ssh: Could not resolve hostname git.sv.gnu.org: Name or service not known
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
Intermittent net failure. I took the liberty of still counting this as
success and manually pushing this staging to master.
Surprising how "dangerous" the manual completion of this Patchy run
feels after a few years of our automated procedure.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
On 28/09/16 10:24, David Kastrup wrote:
pat...@gnu.org writes:
07:29:54 (UTC) Begin LilyPond compile, previous commit at
8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:58 Merged staging, now at:8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:59Success:./autogen.sh --noconfigure
07:30:16Success:/tmp/lilypond-autobuild/configure
--enable-checking
07:30:18Success:nice make clean
07:40:20Success:nice make -j3 CPU_COUNT=3
07:50:03Success:nice make test -j3 CPU_COUNT=3
08:54:44Success:nice make doc -j3 CPU_COUNT=3
08:56:12 *** FAILED STEP ***
merge from staging
Command '['git', 'fetch']' returned non-zero exit status 128
ssh: Could not resolve hostname git.sv.gnu.org: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
08:56:12 Traceback (most recent call last):
File
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line
530, in handle_staging
self.merge_push ()
File
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line
469, in merge_push
run ("git fetch")
File
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line
105, in run
raise FailedCommand ("Command '%s' returned non-zero exit status %d\n%s" %
(cmd, returncode, stderr.strip ()))
FailedCommand: Command '['git', 'fetch']' returned non-zero exit status 128
ssh: Could not resolve hostname git.sv.gnu.org: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Intermittent net failure. I took the liberty of still counting this as
success and manually pushing this staging to master.
Surprising how "dangerous" the manual completion of this Patchy run
feels after a few years of our automated procedure.
Well it is pretty robust, you'd be surprised how many times I get these
kinds of errors over a month (due to repo/network issues).
I've never seen a partial push/merge it fails or it doesn't and if it
fails, then patchy clears up any stale 'lock' branches and starts over.
I'm impressed just how resilient these scripts have been :)
Now if only Jean-Charles, Graham et al, could script checking reg test
diffs and finding obscure make errors in all the .log files we generate ;)
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Proposal: support for custom grob and context properties
On 09/27/2016 09:24 PM, David Kastrup wrote:
Paul writes:
1. Make those two procedures "define-public" so users can just use
them to define their own properties. This requires very minimal
change to LilyPond code, and is convenient for users since existing
functions will just work for accessing and setting their custom
properties (e.g. ly:grob-property).
The problem with the current implementation is that such additions are
not limited in scope and will persist beyond the currently processed
file.
2. Define a "custom-properties" grob property and a "customProperties"
context property (or whatever name) that each holds an alist of user
properties. This adds additional properties to LilyPond and is a
little more complex for the user to work with, but it provides
isolation from LilyPond's properties. (For example, users would only
have to worry about conflicts with other user-defined properties, not
conflicts with current or future LilyPond properties.)
This will not work with current code checks working with object
properties.
I'm interested in implementing this one way or another. Using the
same approach for grob and context properties would make sense.
Thoughts?
First you'd need to move is-grob? and its friends from the old "object
properties" interface to the new, function-calling one. That's an
incompatible change.
Then you'd need to use a session-local defining function for defining
those properties, one that restores the startup state after each
session.
Here is some stone-age patch where you can see how the first step would
look in Scheme (the C++ part would no longer apply since
lily_module_constant has been superseded by the lily-imports.{cc,hh}
files).
All previous such "extensions" dabbling in internals would stop working.
So would previous checks for these properties (it's conceivable to
redefine the old object property accessor functions as they are not
likely to be used outside of LilyPond and a bit of performance impact
for legacy use would be tolerable).
Thanks for the explanation and details. Looks like this is more
involved than I thought... I'll take a closer look, but I suspect this
may be more than I want to take on right now, or at least there are some
other things more within my reach that I'd like to work on first.
-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
