Patchy email

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Patchy email

patchy
15:04:59 (UTC) Begin LilyPond compile, previous commit at 95a26f04acfa14068edff2d4457bfeca12ad80fc
15:05:03 Merged staging, now at: 95a26f04acfa14068edff2d4457bfeca12ad80fc
15:05:03 Success: ./autogen.sh --noconfigure
15:05:19 Success: /tmp/lilypond-autobuild/configure --enable-checking
15:05:22 Success: nice make clean
15:09:28 Success: nice make -j9 CPU_COUNT=9
15:12:41 *** FAILED BUILD ***
        nice make test -j9 CPU_COUNT=9
        Previous good commit: 7583351fbf2f08a4d1f3f0b075fe8b691adc0b95
        Current broken commit: 95a26f04acfa14068edff2d4457bfeca12ad80fc
15:12:41 *** FAILED STEP ***
        merge from staging
        Failed runner: nice make test -j9 CPU_COUNT=9
See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt
15:12:41 Traceback (most recent call last):
  File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 528, in handle_staging
    self.build (issue_id=issue_id)
  File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 328, in build
    issue_id)
  File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 266, in runner
    raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, this_logfilename))
FailedCommand: Failed runner: nice make test -j9 CPU_COUNT=9
See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: Patchy email

David Kastrup
[hidden email] writes:

> 15:04:59 (UTC) Begin LilyPond compile, previous commit at 95a26f04acfa14068edff2d4457bfeca12ad80fc
> 15:05:03 Merged staging, now at: 95a26f04acfa14068edff2d4457bfeca12ad80fc
> 15:05:03 Success: ./autogen.sh --noconfigure
> 15:05:19 Success: /tmp/lilypond-autobuild/configure --enable-checking
> 15:05:22 Success: nice make clean
> 15:09:28 Success: nice make -j9 CPU_COUNT=9
> 15:12:41 *** FAILED BUILD ***
> nice make test -j9 CPU_COUNT=9
> Previous good commit: 7583351fbf2f08a4d1f3f0b075fe8b691adc0b95
> Current broken commit: 95a26f04acfa14068edff2d4457bfeca12ad80fc
> 15:12:41 *** FAILED STEP ***
> merge from staging
> Failed runner: nice make test -j9 CPU_COUNT=9
> See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt
> 15:12:41 Traceback (most recent call last):
>   File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 528, in handle_staging
>     self.build (issue_id=issue_id)
>   File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 328, in build
>     issue_id)
>   File "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 266, in runner
>     raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, this_logfilename))
> FailedCommand: Failed runner: nice make test -j9 CPU_COUNT=9
> See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt
>

This fails in multiple musicxml-converted files.  It's not clear to me
just why from the logs.  I am backing out

commit 1c51a616e289fffb918942c8f1e189ab50809157
Author: Knut Petersen <[hidden email]>
Date:   Fri Jul 19 00:05:00 2019 +0200

    Fix musicxml2ly.py / Python 2.4.5 incompatibility
   
    In LilyPond 2.19.44 code was introduced that
    improved musicxml2ly. Unfortunately, the new
    code introduced a dependency on Python 2.7+,
    although our installers only provide the
    ancient Python 2.4.5.
   
    If our Python 2.4.5 was used to interpret
    musicxml2ly, some parts of the generated
    lilypond source file were ok, in other parts
    every character was paired with an additional
    NUL byte. This commit fixes that problem
    by adding '.encode('utf-8')' at some places.
   
    A 2nd problem was that str.format() was
    used. Unfortunately, str.format() is only
    available in python 2.6+. The patch replaces
    affected code with syntax compatible to our
    Python 2.4.5.

from staging in order to try again.  If you cannot reproduce, I'll try
to see whether I can figure out more after patchy finishes with the
previous revert.

--
David Kastrup

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel