[...] make check-TESTS make[3]: Entering directory '/var/tmp/portage/dev-libs/ppl-1.2/work/ppl-1.2/tests/MIP_Problem' make[4]: Entering directory '/var/tmp/portage/dev-libs/ppl-1.2/work/ppl-1.2/tests/MIP_Problem' PASS: exceptions1 PASS: ascii_dump_load1 PASS: mipproblem4 PASS: mipproblem3 PASS: mipproblem1 ../../test-driver: line 107: 29912 Segmentation fault (core dumped) "$@" > $log_file 2>&1 FAIL: mipproblem2 make[5]: Entering directory '/var/tmp/portage/dev-libs/ppl-1.2/work/ppl-1.2/tests/MIP_Problem' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/var/tmp/portage/dev-libs/ppl-1.2/work/ppl-1.2/tests/MIP_Problem' ============================================================================ Testsuite summary for the Parma Polyhedra Library 1.2 ============================================================================ # TOTAL: 6 # PASS: 5 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/MIP_Problem/test-suite.log Please report to ppl-devel@cs.unipr.it ============================================================================
Created attachment 632546 [details] build.log.xz
Created attachment 632548 [details] test-suite.log
Created attachment 632550 [details] emerge --info
Since this happened while testing glpk-4.65... does the same crash happen with glpk-4.63? I've reported this upstream at $URL.
(In reply to Michael Orlitzky from comment #4) > Since this happened while testing glpk-4.65... does the same crash happen > with glpk-4.63? Yes. Just built 4.63 and tested ppl-1.2 afterwards, all the same. > I've reported this upstream at $URL. Thanks!
Cannot reproduce here. Can you provide /var/tmp/portage/dev-libs/ppl-1.2/work/ppl-1.2/tests/MIP_Problem/mipproblem2.{log,trs} and possibly the output of ldd -r /var/tmp/portage/dev-libs/ppl-1.2/work/ppl-1.2/tests/MIP_Problem/.libs/mipproblem2 please.
I had not noticed it was on ppc64. Sadly, I decommissioned my last ppc64 machine early in February.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4f4a0e1839754410641a5c2f277345f254c4d736 commit 4f4a0e1839754410641a5c2f277345f254c4d736 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2020-04-14 21:20:53 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2020-04-14 21:21:10 +0000 dev-libs/ppl: new revision to work around broken tests. We have a reported test failure on PPC64 that kills the build. There are a few other problematic tests that have been reported upstream as well. Since PPL takes so long to build and test, this commit disables those tests to avoid wasting users' time. Bug: https://bugs.gentoo.org/717258 Upstream-bug: https://www.cs.unipr.it/mantis/view.php?id=2653 Upstream-bug: https://www.cs.unipr.it/mantis/view.php?id=2120 Upstream-bug: https://www.cs.unipr.it/mantis/view.php?id=1078 Upstream-bug: https://www.cs.unipr.it/mantis/view.php?id=2113 Package-Manager: Portage-2.3.89, Repoman-2.3.20 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> dev-libs/ppl/files/disable-boeing-tests.patch | 1176 ++++++++++++++++++++ .../ppl/files/disable-containsintegerpoint1.patch | 38 + dev-libs/ppl/files/disable-mipproblem2.patch | 39 + dev-libs/ppl/metadata.xml | 8 +- dev-libs/ppl/ppl-1.2-r2.ebuild | 67 ++ 5 files changed, 1327 insertions(+), 1 deletion(-)
Can you please try the ppl-1.2-r2 that I just pushed? I've disabled the failing test, but that doesn't mean there aren't more =)
(In reply to Michael Orlitzky from comment #9) > Can you please try the ppl-1.2-r2 that I just pushed? I've disabled the > failing test, but that doesn't mean there aren't more =) I can confirm the build now finishes with all other tests passing.
Great, thanks. I'll call for stabilization of the new revision on another bug.
