Discussion:
Bug#941920: jellyfish: FTBFS on ppc64el
(too old to reply)
Andreas Tille
2019-10-07 16:10:01 UTC
Permalink
Control: tags -1 help
See https://buildd.debian.org/status/logs.php?pkg=jellyfish&arch=ppc64el
I see

============================================================================
Testsuite summary for jellyfish 2.3.0
============================================================================
# TOTAL: 15
# PASS: 10
# SKIP: 4
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0


Since I (but may be others of the team?) have no capacity to debug this
issue on ppc64el my only short term way out would be to deactivate the
specific test.

Any better solution will be welcome

Andreas.
--
http://fam-tille.de
gregor herrmann
2019-10-09 11:30:02 UTC
Permalink
Control: severity -1 important
See https://buildd.debian.org/status/logs.php?pkg=jellyfish&arch=ppc64el
I see
I gave back jellyfish on ppc64el yesterday, and now it built.

https://buildd.debian.org/status/logs.php?pkg=jellyfish&ver=2.3.0-1&arch=ppc64el

Lowering the severity but keeping the bug open as there is something
jellyfishy (sorry for the bad pun) about the package …


Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- BOFH excuse #95: Pentium FDIV bug
Paul Gevers
2019-11-16 07:40:01 UTC
Permalink
Control: severity -1 serious
Control: retitle -1 FTBFS intermittently on buildds ppc64el and amd64
This package failed to build on ppc64el, but 2.2.10-2 in testing built
successfully. So the failure is blocking testing migration.
See https://buildd.debian.org/status/logs.php?pkg=jellyfish&arch=ppc64el
The migration status interferes with the ongoing Perl 5.30 transition,
so it may be necessary to remove this package from testing soon.
This happened again, and now as part of the python-3.8 transition.
Please fix the FTBFS, disabling the test on ppc64el if nothing better
can be thought of.

Also amd64 fails (it hangs *after* the tests):
SKIP: tests/big.sh
PASS: tests/generate_sequence.sh
PASS: tests/bloom_filter.sh
PASS: tests/subset_hashing.sh
PASS: tests/merge.sh
PASS: tests/bloom_counter.sh
PASS: tests/multi_file.sh
PASS: tests/sam.sh
PASS: tests/large_key.sh
PASS: tests/parallel_hashing.sh
SKIP: tests/swig_ruby.sh
PASS: tests/small_mers.sh
PASS: tests/swig_perl.sh
PASS: tests/swig_python.sh
E: Build killed with signal TERM after 150 minutes of inactivity

Paul

Loading...