Re: How to deal with failing 'make test-bseline'

[Thomas Morley]

Am So., 9. Feb. 2020 um 16:35 Uhr schrieb Thomas Morley
<address@hidden>:
>
> Am So., 9. Feb. 2020 um 16:12 Uhr schrieb David Kastrup <address@hidden>:
> >
> > Thomas Morley <address@hidden> writes:
> >
> > > Bringing some offlist-discussion back to the list because it may
> > > interest more people
> > >
> > > Am So., 9. Feb. 2020 um 12:44 Uhr schrieb David Kastrup <address@hidden>:
> > >
> > >> The output of "make test" starts with a line "for tracing crashes, run
> > >> the following command" followed by some obscure grep recipe.  I have no
> > >> idea what this recipe does, but I have no idea how people have a chance
> > >> to find problems without using it.
> > >>
> > >> In this case, it pinpointed the problematic file, and running that
> > >> manually gave the error message in question.
> > >
> > > Ok.
> > > I started from scratch (without #5743), thus 'make test-baseline' 
> > > _should_ fail.
> > > And it does.
> > >
> > > The message
> > > Please see
> > > /home/hermann/lilypond-git/build/out/lybook-testdb/snippet-names-4cf679323625678e6dfeeb9e33801c5e.log
> > > points to a log-file containing nothing else than the version.
> > >
> > > Doing
> > > ~/lilypond-git/build (master)$ grep sourcefilename `grep -L
> > > systems.texi out/lybook-testdb/*/*log|sed s/log/ly/g`
> > > returns:
> > > \sourcefilename "/home/hermann/lilypond-git/input/regression/slur-rest.ly"
> > > Compiling input/regression/slur-rest.ly works like a charm, though.
> > >
> > > So what does this mean?
> >
> > That slur-rest.ly was likely on the slate of LilyPond when this bombed
> > out.
>
> Ok, so how to get a meaningful error-message then?
>
> > Did you manually compile using
> >
> > out/bin/lilypond input/regression/slur-rest.ly
> >
> > or did you use some other command line?
>
> I use a special 'lilypond-git'-command, built after the
> 'lilypond'-command which an installet would put into /bin
> Though, redoing with
> out/bin/lilypond input/regression/slur-rest.ly
> leads to the same result.
>
> > It is worth noting that
> > slur-rest.ly looks very harmless.
> >
> > Only ASCII characters and the single occurence of # is as
> >
> > \layout { ragged-right = ##t }
>
> Yep
>
> >
> > > Am I missing something?
> > > Or is the whole repo corrupted and I should restart with a fesh clone?
> > > (At least this is not the repo I push from...)
> >
> > I don't think corruption can easily explain that.
>
> Anyway, right now I retry with a fresh clone.
> I'll post results later. Will take some time...

I did:

1996  git clone git://git.sv.gnu.org/lilypond.git ~/lilypond-git-2
 1997  cd lilypond-git-2
 1998  git log
 1999  git fetch
 2000  git pull -r
 2001  sh autogen.sh --noconfigure
 2002  mkdir -p build/
 2003  cd build/
 2004  ../configure --enable-guile2
 2005  make
 2006  make test-baseline
 2007  gedit 
/home/hermann/lilypond-git-2/build/out/lybook-testdb/snippet-names-4cf679323625678e6dfeeb9e33801c5e.log
 2008  grep sourcefilename `grep -L systems.texi
out/lybook-testdb/*/*log|sed s/log/ly/g`
 2009  out/bin/lilypond
../input/regression/dynamics-alignment-breaker-linebreak.ly

With similar results, the log-file is mostly empty. The grep-pointed
file compiles fine.

Any idea how to get to the error for display-lily-tests.ly?
We _know_ it must fail. And it fails, if compiled directly, I've checked that.

Thanks,
  Harm