Re: broken doc build (orchestra.ly)

[Phil Holmes]

----- Original Message ----- 
From: "David Kastrup" <address@hidden>
To: "James" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, May 25, 2016 2:43 PM
Subject: Re: broken doc build (orchestra.ly)


> David Kastrup <address@hidden> writes:
>
> > James <address@hidden> writes:
> >
> > > David
> > >
> > > On 24/05/16 18:20, David Kastrup wrote:
> > > > James Lowe <address@hidden> writes:
> > > >
> > > > > No core file was generated, I also upped the ulimit to 1GB.
> > > > >
> > > > > So perhaps it isn't the type of 'assertion' or crash you thought it
> > > > > was after all?
> > > > Perhaps.  Knut's problem, however, sounded like it.  If you have
> > > > different results from Knut, things are even muddier than I thought.
> > > Just in case it isn't obvious :)
> > >
> > > Your checkin stuck in staging is because patchy-staging-merge cannot
> > > complete the make doc so it won't push to staging, not because there
> > > is necessarily anything wrong with your patch.
> >
> > I'll run one of my own.  It's a nuisance that our results differ.  Wait:
> > my patchy runs with --enable-checking instead of --disable-optimising
> > because I have the following patch applied:
>
> [...]
>
> > I'll revert this patch at my end and see whether I get anywhere
> > different.
> >
> > Knut, did you use any options to ./configure ?  config.log should
> > mention how configure was called.
>
> Soooo.  This took longer than I thought because I hibernated the laptop
> (Doh!) before going to sleep.
>
> It completed in the morning.  How-e-ver: staging had already been pushed
> to master previously by someone else.  Did someone test manually?  Or do
> other patchies not fail in the manner Knut's setup does?
>
> --
> David Kastrup


My patchy runs OK at present, so I can test and push to staging.  However, I 
did not do so on this occasion.

--
Phil Holmes