Seanium commented on issue #3099:
URL: https://github.com/apache/hugegraph/issues/3099#issuecomment-5035641661

   Implemented the Server + RocksDB RISC-V scope in #3102.
   
   Key boundaries:
   
   - Only `linux/riscv64` uses the checksum-pinned Alibaba Dragonwell 11 
Extended runtime and automatic `libatomic.so.1` preload.
   - amd64, arm/v7, arm64, ppc64le, and s390x keep the existing 
`eclipse-temurin:11-jre-jammy` runtime.
   - The RocksDB-only reactor/package selection is enabled only for RISC-V. 
Existing architectures keep the default full-backend build and test paths.
   - Native RISC-V protobuf generation uses the system `protoc` and 
`grpc_java_plugin` through automatically activated RISC-V Maven profiles; other 
architectures keep the existing tool resolution.
   
   Executed validation:
   
   - Default Java 11 build: 43/43 reactor modules passed, with the existing 
backend JARs retained.
   - Native RISC-V clean RocksDB-only build: 14/14 modules passed.
   - Native RISC-V runtime on Dragonwell 11 Server VM: RocksDB JNI 
put/get/reopen, REST schema/vertices/edge, Gremlin, health, and restart 
persistence passed.
   - Native RISC-V Core: 794 tests, 0 failures, 0 errors, 41 skipped.
   - Native RISC-V API: 161 tests, 0 failures, 0 errors, 14 skipped; the JaCoCo 
XML was generated and validated.
   - The final Docker helper passed the same JNI, REST, Gremlin, health, and 
restart-persistence flow for linux/amd64, linux/arm64, and linux/riscv64 under 
QEMU. amd64 and arm64 remained on Eclipse Temurin 11 and full-backend 
distributions.
   
   The PR also documents the glibc/LP64D support boundary, Dragonwell runtime, 
Docker/QEMU and native commands, known limitations, and cleanup in 
`hugegraph-server/README.md`.
   
   The published multi-platform manifest/digest check remains a release gate 
because no release image containing this change exists yet. Sustained native 
stress/stability qualification also remains recommended before advertising 
production support. GitHub has not produced hosted check runs for the PR at the 
time of this comment; the results above are the executed native and local/QEMU 
validation, not a claim that those hosted checks ran.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to