A lot of the test failures seen in
https://buildd.debian.org/status/fetch.php?pkg=hmmer&arch=arm64&ver=3.1b2-1&stamp=1436134634
are not easily reproducible.
For example, when I tried
cd testsuite/
touch tmp ; rm tmp* ; ./i9-optional-annotation.pl .. .. tmp
it gave "ok" most of the time, but every now and then it gave
"FAIL: on line 0 target name, dtbl1".
One of the few easily reproducible failures I found on arm64 was this:
touch tmp1 ; rm tmp1* ; ./i8-nonresidues.pl .. .. tmp1
I didn't see that test ever produce a different output from
"FAIL: expected one line in domtbl; saw 2". The "nonresidues"
test also failed on ppc64el. Perhaps you should look at that
one first. Or perhaps you're more worried about the general
non-determinism that affects many of the tests. The obvious question
to ask is: does this non-determinism only exist in the test suite,
or does it also exist in the packaged programs?
