#1103089 jnr-ffi: FTBFS in testing/i386: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/reproducible-path/jnr-ffi-2.2.15 -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/reproducible-path/jnr-ffi-2.2.15/debian -Dmaven.repo.local=/build/reproducible-path/jnr-ffi-2.2.15/debian/maven-repo --batch-mode test returned exit code 1

Package:
src:jnr-ffi
Source:
src:jnr-ffi
Submitter:
Lucas Nussbaum
Date:
2025-08-11 15:25:32 UTC
Severity:
normal
Tags:
#1103089#5
Date:
2025-04-14 11:33:51 UTC
From:
To:
Hi,

During a rebuild of all packages in testing (trixie), your package failed
to build on i386.


Relevant part (hopefully):
The full build log is available from:
http://qa-logs.debian.net/2025/04/14/jnr-ffi_2.2.15-2_testing-i386.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250414;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250414&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

#1103089#10
Date:
2025-04-29 20:50:39 UTC
From:
To:
Interestingly, although upstream doesn't even run tests on i386 [1],
the version in bookworm (2.2.7-1) passed and didn't have issues
running the tests on i386 [2].

One of the flagged assertions was introduced on 2.2.15 [3], so I'll
have to take a closer look as I don't have data confirming if that
test ever passed on i386 in the first place... :(

I guess I'm claiming this bug for myself to be worked on in
MiniDebConfHamburg [4]

#1103089#15
Date:
2025-04-29 21:02:01 UTC
From:
To:
Hello.

In addition to what Lucas reported, this package fails to build for
me on amd64:

82% of the time on machines with 1 CPU
  6% of the time on machines with 2 CPUs

so maybe the issue is not about amd64/i386 but about overall speed.

I suggest that you try on your normal amd64 system using
GRUB_CMDLINE_LINUX="nr_cpus=1".

If that does not work please contact me privately, as I can
offer a VM where this high failure rate happens consistently.

Thanks.

#1103089#20
Date:
2025-05-01 20:24:26 UTC
From:
To:
For now I only could come up with a workaround disabling the unit
tests in all architectures except amd64.

https://salsa.debian.org/java-team/jnr-ffi/-/commit/68b9e6c360b4f27f199af8c564d6ff74d09fa0f2

Upstream doesn't really test on i386. They have support for arm64 but
the required dependency is not available in Debian yet.

In 1 week or so, I'll take a look at the amd64 failures when running
in 1 CPU as reported by Santiago. I'm also observing the tests take
too long, making the build time 30-40 mins, this doesn't make sense
for a normal size library like this one.

Anyway, based on what I find at that point, I'll take a decision to go
with the workaround linked above and/or address the other outstanding
issue(s).