Re: Pango-1.56.4 Test Erros
| Newsgroups | gmane.linux.lfs.beyond.support |
|---|---|
| Message-ID | <[email protected]> |
On 7/31/25 11:20 PM, Randy McMurchy ([email protected] via blfs-support Mailing List) wrote: > Hi all, > > Running the test on the Pango package shows many more errors than what is > listed in the book. Note: > > ================================================= > Summary of Failures: > > 8/29 test-font-data ERROR 0.03s exit status 1 > 9/29 test-bidi ERROR 0.19s killed by signal 6 SIGABRT > 13/29 test-ellipsize ERROR 0.21s killed by signal 6 SIGABRT > 12/29 testiter ERROR 0.24s killed by signal 5 SIGTRAP > 27/29 test-font ERROR 0.24s killed by signal 11 SIGSEGV > 19/29 test-harfbuzz ERROR 0.24s killed by signal 5 SIGTRAP > 20/29 testmisc ERROR 0.24s killed by signal 6 SIGABRT > 29/29 test-layout ERROR 0.31s exit status 1 > > Ok: 18 > Fail: 8 > Skipped: 3 I don't know why you get more errors than I do: Summary of Failures: 1/29 test-font-data ERROR 0.03s exit status 1 22/29 test-font ERROR 0.03s exit status 1 27/29 test-layout ERROR 0.15s exit status 1 Ok: 23 Expected Fail: 0 Fail: 3 Unexpected Pass: 0 Skipped: 3 Timeout: 0 The numbers don't match. but the failure names match yours. This is what I used: mkdir build && cd build && meson setup .. \ --prefix=/usr \ --buildtype=release \ --wrap-mode=nofallback \ -D introspection=enabled && ninja $BFLAGS && echo "BLFS Start CHECK" && (ninja $BFLAGS test || true) && : In my system I used BFLAGS=-j28, but that shouldn't make a difference. The only way I can think of to figure out the failures is to dig into the test code and see what is happening. -- Bruce -- http://lists.linuxfromscratch.org/sympa/info/blfs-support Unsubscribe: See the above information page