[Top][All Lists]

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

Re: Patchy email

From: Phil Holmes
Subject: Re: Patchy email
Date: Tue, 31 Jul 2012 09:45:37 +0100

----- Original Message ----- From: <address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, July 31, 2012 8:00 AM
Subject: Patchy email

04:35:09 (UTC) Begin LilyPond compile, previous commit at 1c980a9906a7ea01b9f99487e75580f7232f2491

04:35:11 Merged staging, now at: 1c980a9906a7ea01b9f99487e75580f7232f2491

04:35:13 Success: ./ --noconfigure

04:35:38 Success: ../configure --disable-optimising

04:35:58 Success: nice make clean

04:42:46 Success: nice make -j2 CPU_COUNT=2 "WEB_TARGETS=online offline"

05:02:14 Success: nice make test -j2 CPU_COUNT=2 "WEB_TARGETS=online offline"

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

lilypond-devel mailing list

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?

Phil Holmes

reply via email to

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