Your message dated Sun, 4 Sep 2016 14:27:57 +0100
with message-id <7861eb9d-de25-4af4-95dd-35873ae05...@gmail.com>
and subject line fixed since version 3.2.x
has caused the Debian Bug report #800384,
regarding arrayfire: random test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
800384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arrayfire
Version: 3.1.2+dfsg1-1
There have been 3 attempts to build this version on the arm64 buildds
between 12:00 and 16:00 today:
https://buildd.debian.org/status/logs.php?pkg=arrayfire&arch=arm64
It was a different machine each time, but each time one of the tests
failed with a segfault, and each time it was a different test:
Attempt 1:
15 - Test_sort_cpu (SEGFAULT)
Attempt 2:
36 - Test_memory_lock_cpu (SEGFAULT)
Attempt 3:
37 - Test_memory_cpu (SEGFAULT)
If these failures are as random as they seem then it would probably
build eventually, with enough tries, but perhaps you want to
investigate this, or suggest how it could be investigated.
The same thing may be happening on some other architectures:
https://buildd.debian.org/status/package.php?p=arrayfire&suite=sid
--- End Message ---
--- Begin Message ---
Manually closing this bug.
The issue has no longer been observed since the 3.2.x versions of
ArrayFire. Debian now ships 3.3.x.
Ghis
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
