lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patchy email


From: John Mandereau
Subject: Re: Patchy email
Date: Tue, 31 Jul 2012 11:20:09 +0200

Il giorno mar, 31/07/2012 alle 09.45 +0100, Phil Holmes ha scritto:
> From: <address@hidden>
> > 04:35:09 (UTC) Begin LilyPond compile, previous commit at 
> > 1c980a9906a7ea01b9f99487e75580f7232f2491
> >
> > 04:35:11 Merged staging, now at: 1c980a9906a7ea01b9f99487e75580f7232f2491

> > 07:00:18 *** FAILED BUILD ***
> >
> > nice make doc -j2 CPU_COUNT=2 "WEB_TARGETS=online offline"
> >
> > Previous good commit:
> >
> > Current broken commit: 1c980a9906a7ea01b9f99487e75580f7232f2491
> >
> > 07:00:18 *** FAILED STEP ***
> >
> > merge from staging
> >
> > Failed runner: nice make doc -j2 CPU_COUNT=2 "WEB_TARGETS=online offline"
> >
> > See the log file 
> > log-staging-nice-make-doc--j2-CPU_COUNT=2-"WEB_TARGETS=online-offline".txt

> I'm confused by this.  AFAICS there's nothing in staging and therefore 
> nothing for patchy to do.  Wonder whether it's local repo got confused by an 
> old non-compiling patch?

No, it's me playing with Patchy, having blanked last_known in the config
file and trying to build with GCC flags for optimization (I already
noticed that this saves 2 minutes on "make test") and install built
documentation to make it available on the web.  I interrupted this build
as configure didn't get CXXFLAGS from the config file.  As the first two
lines of the log show an identical committish, I hoped not to raise
comments, but anyway I have disabled email sending the build I restarted
at 7:30 UTC and will enable it again when I finish a hacking round on
Patchy (I'd also like it to include more logs in the email when it
fails, or copy them to a configurable location for web access).

Cheers,
John




reply via email to

[Prev in Thread] Current Thread [Next in Thread]