Re: PDF builds broken again

On Wed, Jul 23, 2014 at 12:31 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> It seems at least the 9.0 PDFs are broken (trying to build for the release):
>
> Lots of errors/warnings (and AFAIK no way to see which is which in the
> output), but It hink this is the telltale as usual:
>
> Overfull \hbox (7.12454pt too wide) in paragraph at lines 88092--88092
> []\T1/pcr/m/n/9 CREATE FUNCTION getf1(myrowtype) RETURNS int AS 'SELECT $1.f1'
> LANGUAGE SQL;[]
> []
> ....
> and many more like it until
> ....
> Overfull \hbox (1.59999pt too wide) in alignment at lines 241488--241741
> [] [] []
> []
>
> [256.0.1
> ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd
> fstartlink.
> \AtBegShi(at)Output ...ipout \box \AtBeginShipoutBox
> \fi \fi
> l.241875 ...char95{}stat\char95{}file('filename');
>
>
>
> Here is how much of TeX's memory you used:
> 22467 strings out of 482156
> 171125 string characters out of 3785924
> 308594 words of memory out of 3085000
> 27304 multiletter control sequences out of 15000+500000
> 80861 words of font info for 131 fonts, out of 3000000 for 9000
> 14 hyphenation exceptions out of 8191
> 30i,12n,43p,307b,1338s stack positions out of 1500i,500n,1500p,200000b,50000s
> ! ==> Fatal error occurred, no output PDF file produced!
>
>
>
>
> Do we actually have any buildfarm boxes building the PDFs? And if so,
> any idea why they didn't catch it?
>
> Do we have a reasonable way to figure out which commit actually broke
> it, other than manually testing backing out each of the 11 commits
> since 9.0.17?

Additional point of info - the -US pdf's do build on this version,
just not the -A4.

And with even more of those entries about overfull hbox, so clearly
that was not the actual breakage.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/