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.

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]

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.

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).

I took another look at this, but unfortunately I still couldn't find a
good solution.

About a year ago, I pushed a workaround to Salsa to disable test
execution on architectures other than amd64, but I never uploaded
it because, as Santiago mentioned here, the FTBFS bug is still
still present on amd64 when the package is built on a single-CPU system.

I think the most sensible next step would be to update the package
to the latest upstream release and continue investigating from there.

However, I don't expect to have the bandwidth to work on this
in the foreseeable future.

We believe that the bug you reported is fixed in the latest version of
jnr-ffi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1103089@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérôme Charaoui <jerome@riseup.net> (supplier of updated jnr-ffi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 27 Aug 2026 00:15:49 -0400
Source: jnr-ffi
Architecture: source
Version: 2.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Changed-By: Jérôme Charaoui <jerome@riseup.net>
Closes: 1103089
Changes:
 jnr-ffi (2.3.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [Jérôme Charaoui]
   * New upstream version 2.3.1
   * drop -doc package
   * d/control: add libjnr-a64asm-java to build-deps
   * d/control: build using headless jdk
   * d/patches: drop no-ARM64 patch, dependency now packaged
   * d/watch: update to v5 format
   * ignore unwanted maven release plugin
   * Remove redundant Priority: optional from source stanza.
   * Update standards version to 4.7.4, no changes needed.
   * Removed Rules-Requires-Root
 .
   [Miguel Landaeta]
   * Run unit tests only on amd64. Other common architectures
     like arm64 are missing dependencies, i386 and others are not tested
     by upstream, so there is little point to exercise those unsupported
     and/or unreliable targets. (Closes: #1103089)
Checksums-Sha1:
 c464f64954a69b58cd8e34b0ac4bb3359a0d02ee 1664 jnr-ffi_2.3.1-1.dsc
 661c9754050f09f74a2c55fe8e07d0d9c1550c43 285781 jnr-ffi_2.3.1.orig.tar.gz
 719f7f74ffbba9fe6d9009fdfc24dbb93e535049 4716 jnr-ffi_2.3.1-1.debian.tar.xz
 a70a35461e70ed8e656659633cb73d82fb9d802e 12552 jnr-ffi_2.3.1-1_amd64.buildinfo
Checksums-Sha256:
 e0ccc64ddebf73058a9ed88c328ddbde9492893218496a99df737f1964464e08 1664 jnr-ffi_2.3.1-1.dsc
 48e3db1575fc2f335d101fc4b2796e734da7af9bd23be0e6841008f641056f2f 285781 jnr-ffi_2.3.1.orig.tar.gz
 7deb701c5c8d5f931f4996d391e51e3be92692583c1f34f650c9d094a4f7ceb9 4716 jnr-ffi_2.3.1-1.debian.tar.xz
 45087e60372fae0a369ab36d3ec7eb98caef9894d52b92bc202ea41c3db6d10d 12552 jnr-ffi_2.3.1-1_amd64.buildinfo
Files:
 82f2ce2d2269553a6916c7c9caf25dfa 1664 java optional jnr-ffi_2.3.1-1.dsc
 17778c27b3da0c4783d9688b19bb59be 285781 java optional jnr-ffi_2.3.1.orig.tar.gz
 a499483a07d9b75db8d8eadd9d40171c 4716 java optional jnr-ffi_2.3.1-1.debian.tar.xz
 2f20beed0407e19596112338de0d35b8 12552 java optional jnr-ffi_2.3.1-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCao+8MgAKCRBpxS9ljpiF
QtQsAQD2P8b0qMwl2WTFgYAEKOm1ttXH8YCAphPT7por/E1TQAD9GFQSUn6E97XZ
Wr7lXCz6msppC79PncxZrXT5TWTxowQ=
=odUP
-----END PGP SIGNATURE-----