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

2020-02-09 Thread Thomas Morley
Am So., 9. Feb. 2020 um 20:17 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > I've rerun with > > CPU_COUNT=3 make -j3 test > > with success, i.e. the errored file is grepped. > > No idea why more cores help here. > > > I usally use 3 not 5, because of limited memory. > > How limited?

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

2020-02-09 Thread David Kastrup
Thomas Morley writes: > I've rerun with > CPU_COUNT=3 make -j3 test > with success, i.e. the errored file is grepped. No idea why more cores help here. > I usally use 3 not 5, because of limited memory. How limited? What kind of SODIMM could you use for extending? I think there is a reasonab

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

2020-02-09 Thread Thomas Morley
Am So., 9. Feb. 2020 um 19:48 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > 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 `gr

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

2020-02-09 Thread David Kastrup
Thomas Morley writes: > 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 t

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

2020-02-09 Thread Thomas Morley
Am So., 9. Feb. 2020 um 18:03 Uhr schrieb David Kastrup : > > Thomas Morley 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

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

2020-02-09 Thread David Kastrup
Thomas Morley 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 >

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

2020-02-09 Thread Thomas Morley
Am So., 9. Feb. 2020 um 16:35 Uhr schrieb Thomas Morley : > > Am So., 9. Feb. 2020 um 16:12 Uhr schrieb David Kastrup : > > > > Thomas Morley writes: > > > > > Bringing some offlist-discussion back to the list because it may > > > interest more people > > > > > > Am So., 9. Feb. 2020 um 12:44 Uhr

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

2020-02-09 Thread Thomas Morley
Am So., 9. Feb. 2020 um 16:12 Uhr schrieb David Kastrup : > > Thomas Morley 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 : > > > >> The output of "make test" starts with a lin

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

2020-02-09 Thread David Kastrup
Thomas Morley 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 : > >> The output of "make test" starts with a line "for tracing crashes, run >> the following command" followed by some obsc

How to deal with failing 'make test-bseline'

2020-02-09 Thread Thomas Morley
Bringing some offlist-discussion back to the list because it may interest more people Am So., 9. Feb. 2020 um 12:41 Uhr schrieb Thomas Morley : > > Am So., 9. Feb. 2020 um 12:12 Uhr schrieb David Kastrup : > > > > Dan Eble writes: > > > > It would be nice if the test driver would not abort the wh