Re: Patchy email

[Phil Holmes]

----- Original Message ----- 
From: <address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, September 17, 2013 5:37 PM
Subject: Patchy email


> 16:31:10 (UTC) Begin LilyPond compile, previous commit at 
> 88ce02a0c97434ae1b3903395e5664ce2fbf7e35
> 16:31:21 Merged staging, now at: 88ce02a0c97434ae1b3903395e5664ce2fbf7e35
> 16:31:22 Success: ./autogen.sh --noconfigure
> 16:31:42 Success: /tmp/lilypond-autobuild/configure --disable-optimising
> 16:31:51 Success: nice make clean
> 16:37:48 *** FAILED BUILD ***
> nice make -j3 CPU_COUNT=3
> Previous good commit: 75988240e6ba28320ce5d835670712cc09cbd966
> Current broken commit: 88ce02a0c97434ae1b3903395e5664ce2fbf7e35
> 16:37:48 *** FAILED STEP ***
> merge from staging
> Failed runner: nice make -j3 CPU_COUNT=3
> See the log file log-staging-nice-make--j3-CPU_COUNT=3.txt
> 16:37:48 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 -j3 CPU_COUNT=3
> See the log file log-staging-nice-make--j3-CPU_COUNT=3.txt

That's a surprise.  I ran make doc on that commit and it passed OK.  I've 
got a few minutes before leaving for a rehearsal - I'll try a clean make. 
If the logfile is available, I'd like to see it.

--
Phil Holmes