Dear maintainer(s),

I looked at the results of the autopkgtest of your package (it showed up
for the glibc security update in stable). I noticed that it regularly
fails on several architectures, mostly on i386, due to a segfault. (On
s390x and riscv64 it always fails, the logs I checked were also due to
segfault).

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/i386/h/hilive/38615295/log.gz

142s Could not finish output for cycle 100.
142s Waiting for output tasks...
142s Finished output tasks.
142s
142s
142s stack trace:
142s   0        [0x56637ea2]  hilive(+0x16ea2)
142s   1        [0xf7f355a0]  __kernel_sigreturn + 0
142s   2        [0x56724027]  hilive(+0x103027)
142s   3        [0x56662b42]  hilive(+0x41b42)
142s   4        [0x56667d70]  hilive(+0x46d70)
142s   5        [0x56667e02]  hilive(+0x46e02)
142s   6        [0x56637d2d]  hilive(+0x16d2d)
142s   7        [0x566389cd]  hilive(+0x179cd)
142s   8        [0x5663929c]  hilive(+0x1829c)
142s   9        [0xf7ac008d]  /lib/i386-linux-gnu/libstdc++.so.6(+0xc008d)
142s  10        [0xf768791d]  /lib/i386-linux-gnu/libc.so.6(+0x8791d)
142s  11        [0xf77211c8]  /lib/i386-linux-gnu/libc.so.6(+0x1211c8)
142s
142s
/tmp/autopkgtest-lxc.0511cpj5/downtmp/build.F2k/src/debian/tests/run-unit-test:
line 23:   975 Segmentation fault      hilive -b BaseCalls -i index/hiv1
-r 100R --lanes 1 --tiles 1101