RFR: 8352730: RISC-V: Disable tests in qemu-user

[Robbin Ehn]

On Tue, 25 Mar 2025 14:19:55 GMT, Robbin Ehn <rehn at openjdk.org> wrote:

> Hi, for you to consider.
> 
> These tests constantly fails in qemu-user.
> Either the require host to be same arch or they are very very slow in emulation.
> E.g. "ptrace(PTRACE_ATTACH, ..) failed for 405157: Function not implemented'" for SA tests.
> This is the initial set of tests, there are many more, but I need to do some more verification for those.
> 
> From bug:
>> qemu-user/rv64 sets uarch to "qemu" in /proc/cpuinfo (qemu-system do not do that).
>> We add this uarch to CPU feature string.
>> This means we can use jtreg 'require' with cpu string to filter out tests in qemu-user.
> 
> Relevant qemu code:
> https://github.com/qemu/qemu/blob/170825d14d88a1ce7fae98d5a928480f2f329b22/linux-user/riscv/target_proc.h#L29
> 
> Relevant hotspot code:
> https://github.com/openjdk/jdk/blob/fa0b18bfde38ee2ffbab33a9eaac547fe8aa3c7c/src/hotspot/os_cpu/linux_riscv/vm_version_linux_riscv.cpp#L250
> 
> Tested that the require only filters out tests in qemu+riscv64.
> 
> Thanks!
> 
> /Robbin

Yes, it's much solver as you can't use a compile jdk.
Note that is not a full tier1, "make test-tier1"
Which means you have a day or two more for a full tier1.

There are plenty of test in the jdk which stress or correctness test runtime/compiler, e.g.:
test/jdk/java/lang/Thread/virtual/MonitorWaitNotify.java
test/jdk/java/lang/Float/Binary16Conversion.java

`make test-tier1 CONF=linux-riscv64-server-fastdebug JTREG="OPTIONS=-e:QEMU_LD_PREFIX=/usr/riscv64-linux-gnu/;JAVA_OPTIONS=;RETAIN=all" JDK_FOR_COMPILE=/home/rehn/source/jdk/vanilla/build/linux-x86_64-server-release/images/jdk JTREG_TIMEOUT_FACTOR=20`

One issue with high timeout factor is that make+jtreg only can parallelize tests in the same directory.
Which means you often end up with just waiting for one test to complete before anything else can happen.

Hotspot tier1 takes around 8h with timeout factor 20 for me in qemu-user, cpu = max, but tests still timeout.
Even when running JOBS=1 some timeout, at least on cpu = max.
Hence this enhancement :)

-------------

PR Comment: https://git.openjdk.org/jdk/pull/24229#issuecomment-2753357500