Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

[Chris Yate]

On Fri, 6 Jan 2017 at 12:23 Thomas Morley <address@hidden> wrote:

> 2017-01-06 13:10 GMT+01:00 Chris Yate <address@hidden>:
>
> >
> > Curiously, this didn't fail with assertions. I've just upgraded to
> 2.19.54,
> > and the test cases that crashed for me previously still crash :)
> >
> > Log attached (although I don't think this will be very helpful).
>
>
>
> Strange that your log file (I assume default loglevel) differs
> significantely from mine.
> Seems the order what is done at which time is very different.
>
> $ lilypond manual-breaking-assertion-failure-04.ly
> GNU LilyPond 2.19.52
> Processing `manual-breaking-assertion-failure-04.ly'
> Parsing...
> Interpreting music...
>         Compiling: TEST 1a
>
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 1b
>
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 1c
>
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 1d
>
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 2a
>
> [8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320]
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 2b
>
> [8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320]
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 2c
>
> [8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320]
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 2d
>
> [8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320]
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 3a
>
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 3b
>
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 3c
>
> Preprocessing graphical objects...
> Interpreting music...
>         Compiling: TEST 3d
>
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 9 or 10 pages...
> Drawing systems...
> warning: compressing over-full page by 93.7 staff-spaces
> warning: page 2 has been compressed
> warning: compressing over-full page by 93.7 staff-spaces
> warning: page 4 has been compressed
> Layout output to `/tmp/lilypond-v8vCX0'...
> Converting to `manual-breaking-assertion-failure-04.pdf'...
> Deleting `/tmp/lilypond-v8vCX0'...
> Success: compilation successfully completed
>
>
> May there be the problem with the assertion?
>
> Cheers,
>   Harm
>

 Here's mine without 3x tests. I didn't change the loglevel.

The different order is probably explained by the redirection I previously
used to send stdout and stderr to the same file!
(i.e.  c:\> lilypond <input file>  > output.txt 2>&1 ). For this one I've
just cut and pasted from the shell.

But I saw no assertions get thrown here; I think they're swallowed for some
reason, because if I comment all but, say 2a, then it does terminate with
an error.

Chris

manual-breaking-assertion-failure-04.output_without3x.txt
Description: Text document