Bug#1103106: libmina-sshd-java: FTBFS: flaky tests

Santiago Vila sanvila at debian.org
Sun Dec 14 11:47:55 GMT 2025


severity 1103106 important
thanks

Hello.

This package used to ftbfs for me some time ago, but its status
seems to have changed a little bit in the last months.

Currently, I have it in the category "ftbfs randomly on single-cpu
systems" and also "builds ok on machines with 2 cpus", but the build
history on single-cpu is like this:

Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250412T044806.335Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250413T045013.222Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250414T044802.062Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250415T044801.538Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250416T044807.142Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250417T044805.941Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250419T043803.148Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250420T043703.327Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250421T043804.535Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250423T041114.822Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250424T043803.440Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250425T043702.920Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250426T043703.449Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250427T043806.248Z
Status: failed      libmina-sshd-java_2.13.2-2_amd64-20250428T043806.768Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250503T051134.191Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250614T174517.455Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250620T044012.895Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250620T044013.769Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250802T100714.828Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250820T094416.981Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250821T040830.119Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20250822T040855.400Z
Status: successful  libmina-sshd-java_2.13.2-2_amd64-20251004T032435.217Z
Status: successful  libmina-sshd-java_2.13.2-3_amd64-20251005T085803.892Z


This can be due to a series of factors:

It could be that it does not fail anymore when using the kernel of
trixie.

It could also be that some build-dependency which triggered this
failure has been fixed in the meantime.

Ot it could be that it does not fail anymore when using sbuild and the
unshare backend, to which I switched some time ago as the default.

In fact, in the above build history, the latest build logs are most
probably using the unshare backend, while the older ones are probably
using the old file backend, so this is my current best theory.


So, I'm going do some additional checks to understand the true nature
of the bug. In the meantime I'm downgrading to important, as I feel a
serious severity does not fit with available data.

Thanks.



More information about the pkg-java-maintainers mailing list