[Debichem-devel] Bug#848781: tiledarray: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

Lucas Nussbaum lucas at debian.org
Mon Dec 19 21:26:11 UTC 2016


Source: tiledarray
Version: 0.4.4-2
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/CMakeFiles 0
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/tests'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    debian/rules override_dh_auto_test
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> export OMPI_MCA_plm_rsh_agent=/bin/false
> (cd obj-*/tests; mpiexec -np 2 ./ta_test)
> MADNESS runtime initialized with 63 threads in the pool and affinity -1 -1 -1
> Running 393 test cases...
> Running 393 test cases...
> unknown location(0): fatal error: in "distributed_storage_suite/array_operator": memory access violation at address: 0x7f53709e95d0: no mapping at fault address
> /<<PKGBUILDDIR>>/tests/distributed_storage.cpp(102): last checkpoint: "array_operator" entry.
> unknown location(0): fatal error: in "distributed_storage_suite/array_operator": memory access violation at address: 0x7fc69c66f5d0: no mapping at fault address
> /<<PKGBUILDDIR>>/tests/distributed_storage.cpp(102): last checkpoint: "array_operator" entry.
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/tiledarray_0.4.4-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the Debichem-devel mailing list