There is 1 open security issue in trixie.
There is 1 open security issue in forky.
commit e19eb005969dc735c566156f7478276a0eacb6f8
Author: Vladimir Petko <vladimir.petko@canonical.com>
Date: Thu Nov 12 14:47:54 2026 +1300
changelog
commit 2f96c24df20e841cb926d27f54e7652ba673c441
Author: Na Zhang <zhangna@loongson.cn>
Date: Mon Oct 26 14:25:55 2026 +0800
lower the jtreg timeout factor to 10 on loong64 and riscv
jtreg applies the factor to the timeouts declared by the tests themselves
as well, not only to the 120s default, and the hotspot suite declares
timeouts of up to 180000s. With factor 30 a single test hanging in the
zero VM can keep the harness silent for hours and the buildds kill a build
after 150 minutes without output.
Keep factor 10 and pass -tl:480 to skip tests declaring a timeout we
cannot afford to wait for; jtreg reports them as "did not meet time-limit
requirements", not as failures. Worst case silence is now 480s * 10 =
80 minutes.
Among the 40 debian patches available in version 25.0.5.0.3+1-3 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/o/openjdk-25.png){kind=link}