test-code-cache fails on a Linux/riscv64 build with FFI enabled. #64717

Activity

1. sxa

   added

   riscv64Issues and PRs related to the 64-bit RISC-V architecture.Issues and PRs related to the 64-bit RISC-V architecture.

   on Jul 24, 2026
2. sxa commented on Jul 24, 2026

   

   sxa

   on Jul 24, 2026

   MemberAuthor

   More actions

   @nodejs/ffi @joyeecheung i haven't gone digging yet but would any of you have any idea why enabling FFI in the build might be breaking this test? I'm assuming this hasn't been spotted on any other platform so far and really is specific to Linux/riscv64.
3. daeyeon

   added

   ffiIssues and PRs related to experimental Foreign Function Interface support.Issues and PRs related to experimental Foreign Function Interface support.

   on Jul 24, 2026
4. kxxt commented on Jul 25, 2026

   

   kxxt

   on Jul 25, 2026

   Member

   More actions

   Which means the parallel/test-code-cache problem seems to be the one remaining that will need addressing. Noting that node -pe 'process.config.variables.node_use_node_code_cache' returns true on the native builds but false on the unofficial (cross-compiled) builds so those pass. It looks like it started failing when the FFI support was added, and I've confirmed (sample size of 1!) that building with --without-ffi seems to allow that test to pass. We need to understand why this might only be affecting RISC-V so I'll split out another issue to cover this failure.

   Hmm, I didn't encounter this test failure with a native build on SG2042.

   Test logs available at https://github.com/riscv-forks/node-riscv/actions/runs/30152090741/job/89671914200.

   ./node  -pe 'process.config.variables.node_use_node_code_cache'
   true
   <]$ out/Release/node test/parallel/test-code-cache.js                        
   NOTE: The test started as a child_process using these flags: [ '--expose-internals' ] And these environment variables: {} Use NODE_SKIP_FLAG_CHECK to run the test with the original flags.
   (node:1603257) internal/test/binding: These APIs are for internal testing only. Do not use them.
   (Use `node --trace-warnings ...` to show where the warning was created)
   (node:1603257) internal/test/transfer: These APIs are for internal testing only. Do not use them.
   (node:1603257) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
   [kxxt@centiskorch node-riscv]$ echo $?
   0
   [kxxt@centiskorch node-riscv]$ ./node --experimental-ffi -e "require('node:ffi');console.log('ffi is enabled')"                               
   ffi is enabled
   (node:1603620) ExperimentalWarning: FFI is an experimental feature and might change at any time
   (Use `node --trace-warnings ...` to show where the warning was created)
   
5. kxxt commented on Jul 25, 2026

   

   kxxt

   on Jul 25, 2026

   Member

   More actions

   would any of you have any idea why enabling FFI in the build might be breaking this test?

   The last time I encounter such weird issues is that configuring node.js with --shared broke some tests on riscv64. But it later turned out to be a mis-compilation done by GCC (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116057). Maybe it is worthwhile to check the compiler version and if you could reproduce it with clang.
6. sxa commented on Jul 27, 2026

   

   sxa

   on Jul 27, 2026

   Last edited by sxa

   MemberAuthor

   More actions

   Thanks for confirming - most of the stuff I'm doing at the moment is with Bianbu's clang22 and yeah it's looking quite likely that it's specific to that compiler. I've just checked with a v26 build produced with clang-21 on another machine that doesn't seem to show the problem.
   I'll give it a shot with clang-21 from the Bianbu since that version seems to be available in their repos.
7. sxa commented on Jul 27, 2026

   

   sxa

   on Jul 27, 2026

   Last edited by sxa

   MemberAuthor

   More actions

   OK looks like the test passes when it's built with clang-21 on the same machine so there's something in clang-22 that's breaking this. <<< Incorrect - I misread the logs unfortunately due to the failure not showing where I expected. It doesn't seem to be a problem with clang-22 on x64 (tested with the version in the Fedora44 repositories in a container).

   I'll try and see if it will build with gcc ...
8. sxa commented on Aug 4, 2026

   

   sxa

   on Aug 4, 2026

   MemberAuthor

   More actions

   Seems to pass ok with Node 26 built with gcc 15 🤔