[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debug make test failure

From: Jean Abou Samra
Subject: Re: Debug make test failure
Date: Tue, 6 Oct 2020 00:48:46 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

Le 06/10/2020 à 00:40, Jean Abou Samra a écrit :

Le 05/10/2020 à 10:08, Jonas Hahnfeld a écrit :
Am Montag, den 05.10.2020, 00:24 +0200 schrieb Jean Abou Samra:

I'm tracking down a failure of make test


 From this, is there a way I can view which file failed?
The build system tells you:

To begin investigating regression-test crashes, use
     grep sourcefilename `grep -L systems.texi out/lybook-testdb/*/*log|sed s/log/ly/g`

Thanks, but this hangs as "grep -L systems.texi out/lybook-testdb/*/*log" returns no matches, so the second grep starts reading standard input. Not sure why the failed files are not detected?

Got it: the test I added contained an obvious syntax error made while saving, but since LilyPond did a good job it still managed to produce a PDF, and "systems.texi" appeared in the log.

Not sure wether there is a way to look for failed files more reliably. In the meantime, I found

cd input/regression
LC_ALL=C lilypond -d job-count=9 *.ly

to work well (LC_ALL=C needed because warnings are expected in English...)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]