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

[Thomas Morley]

Am So., 9. Feb. 2020 um 18:03 Uhr schrieb David Kastrup <address@hidden>:
>
> Thomas Morley <address@hidden> writes:
>
> > 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.
>
> Differences to what I do:  I use
>
> CPU_COUNT=9 make -j9 test
>
> Namely more than one CPU, and I first make test rather than
> test-baseline.  I have no idea why that would make a difference.
>
> --
> David Kastrup


I now tried
 2014  make test-clean
 2015  make test
with no useful infos, like before

but
 2020  make test-clean
 2021  CPU_COUNT=9 make -j9 test
 2022  grep sourcefilename `grep -L systems.texi
out/lybook-testdb/*/*log|sed s/log/ly/g`
finally pointed to input/regression/display-lily-tests.ly

I always thought a multi-core run is more difficult to debug ...
Of course 9 cores is pretty pointless here. I've two behaving like 4...

Cheers,
  Harm