Dear maintainers,

Compiling the openjdk-26 failed for loong64 in the Debian Package
Auto-Building environment.
The error log is as follows,
```
......
Passed: compiler/loopopts/TestPartialPeelAtUnsignedTests.java
Error:
compiler/loopopts/TestPartialPeelAtUnsignedTestsNegativeLimit.java#Xbatch
Error:
compiler/loopopts/TestPartialPeelAtUnsignedTestsNegativeLimit.java#Xcomp-compile-test
Error:
compiler/loopopts/TestPartialPeelAtUnsignedTestsNegativeLimit.java#Xcomp-run-inline
Passed: compiler/loopopts/TestPartialPeelingAtSingleInputRegion.java
Passed: compiler/loopopts/TestPeelingNeverEnteredLoop.java
FAILED: compiler/loopopts/TestPeelingSkeletonPredicateInitialization.java
Passed: compiler/loopopts/TestPhaseCFGNeverBranchToGotoMain.java#id0
Passed: compiler/loopopts/TestPhaseCFGNeverBranchToGotoMain.java#id1
FAILED: compiler/loopopts/TestPredicateInputBelowLoopPredicate.java
Passed: compiler/loopopts/TestPreMainPostFallInEdges.java
Passed: compiler/loopopts/TestRCEAfterUnrolling.java
FAILED: compiler/loopopts/TestReassociateInvariants.java
......
```
The full build log can be found at
https://buildd.debian.org/status/fetch.php?pkg=openjdk-26&arch=loong64&ver=26%7E22ea-2&stamp=1762629065&raw=0.
Please consider the patch I attached.
Currently, OpenJDK can only be built with the Zero variant on loong64.
I have built openjdk-26 successfully on locally.
Your opinions are welcome.

Best regards,
Dandan Zhang

Please don't disable the tests anymore, at least you want to become a
release architecture ...

Please just disable the tests which are timing out.

Please don't disable the tests anymore, at least you want to become a
release architecture ...

Please just disable the tests which are timing out.

Hi,

Unfortunately I do not have access to loong64 architecture. Could you
please identify failing tests and add those to
debian/tests/problems.csv.
The format of the file: Test,Bug,Comment,Packages,Arch,Release.

For loong64 tests failing in openjdk-26 the lines could look line
---
FAILED: java/foreign/StdLibTest.java,<link to upstream bug, optional>,
Short summary of the issue,:openjdk-26,:loong64,:release-all
---
Best Regards,
 Vladimir.

Hi Vladimir,

Debian Developers can use shenzhou.debian.net, see:

https://db.debian.org/machines.cgi?host=shenzhou

Everyone else can use the loong64 machines in the GCC compile farm:

https://gcc.gnu.org/wiki/CompileFarm

Adrian

On Sat, 29 Nov 2025 15:43:09 +0100 Matthias Klose wrote:
 > Control: tags -1 - patch
 >
 > Please don't disable the tests anymore, at least you want to become a

 > release architecture ...

Please consider adding loong64 to this arch lists.

  with_check = $(if $(findstring nocheck, $(DEB_BUILD_OPTIONS)),,yes)
-ifneq (,$(filter $(DEB_HOST_ARCH), alpha arc armel mipsel mips64el 
powerpc riscv64 x32))
+ifneq (,$(filter $(DEB_HOST_ARCH), alpha arc armel loong64 mipsel
mips64el powerpc riscv64 x32))
    with_check = disabled running check on $(DEB_HOST_ARCH)
  endif

For openjdk-21 21.0.10~4ea-1, you removed loong64 from above lists.
https://buildd.debian.org/status/logs.php?pkg=openjdk-21&arch=loong64

Since penjdk-26 26~21ea-1, you removed loong64 from above lists.
https://buildd.debian.org/status/logs.php?pkg=openjdk-26&arch=loong64

Currently, OpenJDK can only be built with the Zero variant on loong64.

Thanks.

again, please don't just disable running the tests. Please provide an
exclude list not to run problematic tests.

Hi Dandan,

Matthias is absolutely right! Turning off all tests might be okay for Debian Ports,
it's definitely not okay for Debian's release architectures.

Please follow Vladimir's advise and add the failing tests to debian/tests/problems.csv.

Adrian

Hi,

It seems that there is no native LoongArch64 acceleration in openjdk, so tests
involving massive loops will take very long to finish. I have kept the build
running for 36 hours and found out the following tests should be omitted to
make openjdk tests overcome the default 150 min of stalled package timeout
of sbuild.

serviceability/jvmti/thread/SuspendThreadList/suspendthrdlst01/suspendthrdlst01.java
serviceability/jvmti/thread/ResumeThreadList/resumethrdlst02/resumethrdlst02.java
serviceability/jvmti/thread/SuspendThread/suspendthrd01/suspendthrd01.java
serviceability/jvmti/thread/ResumeThreadList/resumethrdlst01/resumethrdlst01.java
serviceability/jvmti/thread/ResumeThread/resumethrd02/resumethrd02.java
serviceability/jvmti/thread/ResumeThread/resumethrd01/resumethrd01.java
serviceability/jvmti/thread/GetThreadState/thrstat02/thrstat02.java
serviceability/jvmti/thread/GetCurrentContendedMonitor/contmon02/contmon02.java
serviceability/jvmti/thread/GetCurrentContendedMonitor/contmon01/contmon01.java
serviceability/jvmti/SuspendWithCurrentThread/SuspendWithCurrentThread.java
runtime/NMT/SummaryDiffThreadCount.java
runtime/lockStack/TestStackWalk.java
compiler/loopopts/TestRemoveEmptyLoop.java
jdk/internal/shellsupport/doc/JavadocHelperTest.java

The following two tests also take relative long time to finish. If disabling
the above tests is not enough to finish the compile on the buildd machines, these
can also be disabled.

compiler/intrinsics/sha/TestDigest.java
serviceability/jvmti/vthread/PopFrameTest/PopFrameTest.java

Cheers,

Miao Wang

Hello Miao,

Would you mind sending a patch for the Debian package?

You can open a pull request on Salsa [1].

Adrian

the rules file starts a buildwatch.sh to avoid that. Do you know why it
would not be working?

Matthias

Hi,

I have opened https://salsa.debian.org/openjdk-team/openjdk/-/merge_requests/253

Cheers,

Miao Wang

Hi,

I have no idea why this mail failed to arrive in my mailbox. buildwatch.sh
is not relevant to this problem since it only works during the build stage
but the timeout happens during executing the tests.

Cheers,

Miao Wang