xuxiaowei-com-cn commented on PR #8165:
URL: https://github.com/apache/incubator-seata/pull/8165#issuecomment-5127077571

   @funky-eyes 
   
   1. Done
   2. Done, using 
test-suite/test-native-metadata-merge/src/test/java/org/apache/seata/metadata/ExecuteMergeNativeImageMetadataTests.java
   3. Done, same as above
   4. Done, see: install-namingserver-native, package-namingserver-native
   5. Done, see commit c165c028
      1. Tests have been added in 
test-suite/test-native-namingserver/src/test/java/org/apache/seata/namingserver
      2. The existing reachability-metadata.json data comes from 
https://github.com/xuxiaowei-com-cn/incubator-seata/actions/runs/30513683171
         
namingserver-macos-26-997d0d9b5c6fc11a0b46ff3c4329222ce538d083-reachability-metadata
 (fully reproducible),
         and is already the most comprehensive (covering Linux ARM, Linux AMD, 
Windows).
      3. According to the subsequent Artifacts from 
https://github.com/xuxiaowei-com-cn/incubator-seata/actions/workflows/schedule-native-namingserver-metadata.yml,
         no diff has been generated so far, indicating that the existing 
reachability-metadata.json is already the most complete data
   6. Done, same as above
   7. Done
   8. Although Linux uses dynamically linked libraries, it can run as long as 
ldd version is greater than 2.32. Common Docker image ldd versions can be found 
at: https://xuxiaowei.io/t/ldd/52
      Personally tested on a debian 12.0 (released June 2023) Docker image, and 
it runs normally
      
       <img width="698" height="178" alt="image" 
src="https://github.com/user-attachments/assets/32a6605f-e5f1-4ac1-a381-447ab6e5908a";
 />
       
       <img width="1989" height="1055" alt="img" 
src="https://github.com/user-attachments/assets/89bb4fa2-7dcf-4398-9ac3-73cfa9f177ad";
 />
   
   9. Comments have been added in .github/workflows/native-namingserver.yml
   10. See 5
   


-- 
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