[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Anything wrong with patchy-staging?
From: |
James Lowe |
Subject: |
Re: Anything wrong with patchy-staging? |
Date: |
Sat, 11 Jul 2015 17:49:44 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 |
On 11/07/15 17:46, James Lowe wrote:
> On 11/07/15 17:07, David Kastrup wrote:
>>
>> Issue 4475 has been pushed about 3.5h ago to staging. I thought
>> we had a Patchy-staging run about every 2 hours? Does this mean
>> that there has been a failure?
>>
>> Problem is that I'm likely off in about an hour, and if I start a
>> Patchy-staging run now, it will not be finished before I am
>> gone. And I'd like to push my remaining issues to staging anyway
>> but would prefer not having to rebase everything in case the
>> current staging _is_ rotten.
>>
>> So is there anything worth noting concerning the current state of
>> staging and/or Patchy?
>
> Its that same error we had yesterday when I was testing patches I
> think
No it isn't. But anyway...
>
> --snip--
>
> address@hidden /tmp$ more
> build-lilypond-autobuild/input/regression/collated-files.texilog.log
>
>
*** '}' without opening '{' before: . The pitches in
> @code{\autochange} are (in out-test/autochange-r elative.texidoc l.
> 3)
>
> --snip--
>
> It's failing on the make test part of patchy staging
This commit
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=d8c4e11ec4b595ef3db652b89c3d3163ba9235c5
James