Patchy email

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

Patchy email

patchy
22:26:26 (UTC) Begin LilyPond compile, previous commit at 83045b846acb4aaadf54373941a915c4c45fb522
22:26:34 Merged staging, now at: 83045b846acb4aaadf54373941a915c4c45fb522
22:26:35 Success: ./autogen.sh --noconfigure
22:26:47 Success: /tmp/lilypond-autobuild/configure --enable-checking
22:26:51 Success: nice make clean
22:30:49 *** FAILED BUILD ***
        nice make -j9 CPU_COUNT=9
        Previous good commit: 786c3669ff08804465a89013d349fc745fd783c9
        Current broken commit: 83045b846acb4aaadf54373941a915c4c45fb522
22:30:49 *** FAILED STEP ***
        merge from staging
        Failed runner: nice make -j9 CPU_COUNT=9
See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt
22:30:49 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 316, 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 -j9 CPU_COUNT=9
See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt

Reply | Threaded
Open this post in threaded view
|

Re: Patchy email

David Kastrup
[hidden email] writes:

> 22:26:26 (UTC) Begin LilyPond compile, previous commit at 83045b846acb4aaadf54373941a915c4c45fb522
> 22:26:34 Merged staging, now at: 83045b846acb4aaadf54373941a915c4c45fb522
> 22:26:35 Success: ./autogen.sh --noconfigure
> 22:26:47 Success: /tmp/lilypond-autobuild/configure --enable-checking
> 22:26:51 Success: nice make clean
> 22:30:49 *** FAILED BUILD ***
> nice make -j9 CPU_COUNT=9
> Previous good commit: 786c3669ff08804465a89013d349fc745fd783c9
> Current broken commit: 83045b846acb4aaadf54373941a915c4c45fb522
> 22:30:49 *** FAILED STEP ***
> merge from staging
> Failed runner: nice make -j9 CPU_COUNT=9
> See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt
> 22:30:49 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 316, 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 -j9 CPU_COUNT=9
> See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt
>
>

makeinfo.notation.log states:

out/notation/rhythms.texi:1961: misplaced {
out/notation/rhythms.texi:1961: misplaced }

The respective line appears to be:

the note name uppercase @example{R}.  Their duration is entered

@example is not an in-text command but rather an environment.

Backing out the respective commit from staging.

All the best.

--
David Kastrup

Reply | Threaded
Open this post in threaded view
|

Re: Patchy email

Werner LEMBERG
> makeinfo.notation.log states:
>
>   out/notation/rhythms.texi:1961: misplaced {
>   out/notation/rhythms.texi:1961: misplaced }
>
> The respective line appears to be:
>
>   the note name uppercase @example{R}.  Their duration is entered
>
> @example is not an in-text command but rather an environment.
> Backing out the respective commit from staging.

Oops, I gave wrong advice, sorry.  Please do

  s/@example/@samp/

and re-commit.


    Werner

Reply | Threaded
Open this post in threaded view
|

Re: Patchy email

Valentin Villenave-3
On 3/25/20, Werner LEMBERG <[hidden email]> wrote:
> Oops, I gave wrong advice, sorry.

You’re not the one to blame; I was the one who jumped the gun.

> Please do
>   s/@example/@samp/
> and re-commit.

Done. Aand this is why we have a patch reviewing process. Lesson
learned. (Again.)

V.