James Lowe <[email protected]> writes:
> 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
>
> --snip--
>
> james@james-OptiPlex-990 /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
Yeah, just got the complaint from my "server in France".
It's obviously
@{\\autochange}.
in a comment from Dan. Always a risk when pushing something that has
not been tested in that form.
Ok, so I'll back out the commit from Dan and put my commits in instead.
And then I'll have to be off.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
