#1151157 src:openjdk-27: fails to migrate to testing for too long: FTBFS on loong64 (hangs)

#1151157#5
Date:
2026-10-17 14:00:59 UTC
From:
To:
Source: openjdk-27
Version: 27~34ea-1
Severity: serious
Tags: sid forky ftbfs
User: release.debian.org@packages.debian.org
Usertags: out-of-sync
User: debian-loongarch@lists.debian.org
Usertags: loong64
X-Debbugs-CC: debian-loongarch@lists.debian.org

Dear maintainer(s), porters,

[Summary: openjdk-27 FTBFS on loong64, tail of the log at the end.]

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Critical bug in
testing [1]. Your package src:openjdk-27 has been trying to migrate for
31 days [2], hence this bug report. The current output of the migration
software for this package is copied to the bottom of this report and
should list the reason why the package is blocked. Regularly, reporting
issues against reverse (build/test/regular) dependencies is what needs
to happen. If this has already been done, than this bug is just for
tracking purposes.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Blocked packages can have impact on other packages,
which makes preparing for the release more difficult. The situation that
caused this bug report might even be the result of such an issue. We
expect maintainers to fix issues that hamper the migration of their
package in a timely manner. If your package in this situation due to
another package, consider helping out.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=openjdk-27

Current text from [2]:
Migration status for openjdk-27 (27~34ea-1 to 27+35-2): BLOCKED: Maybe
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on loong64
∙ ∙ Missing build on riscv64
∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
∙ ∙ Autopkgtest for libreoffice/4:26.8.1.1-3: amd64: Pass, arm64: Test
triggered (failure will be ignored), armhf: Test triggered (failure will
be ignored), i386: Test triggered (failure will be ignored), ppc64el:
Pass, s390x: Pass
∙ ∙ Autopkgtest for openjdk-27/27+35-2: amd64: Pass, arm64: Test
triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el:
Test triggered (failure will be ignored), s390x: Pass
∙ ∙ Lintian check waiting for test results on loong64, riscv64 - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/o/openjdk-27.html
∙ ∙ Not reproduced on amd64 (not a regression): openjdk-27-jdk
∙ ∙ Not reproduced on arm64 (not a regression): openjdk-27-jdk
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 9 days old (needed 5 days)

https://buildd.debian.org/status/fetch.php?pkg=openjdk-27&arch=loong64&ver=27%2B35-2&stamp=1791576877&raw=0

Passed: serviceability/tmtools/jstat/GcTest02.java
E: Build killed with signal TERM after 150 minutes of inactivity
--------------------------------------------------------------------------------
Build finished at 2026-10-09T20:14:27Z