Single Executable Application tests often fail on RISC-V

[sxa]

The SEA tests are failing in many cases. The symptoms are different depending on the hardware. Using a build of Node v25.2.2 I'm currently getting:

• SIGILL on a TH1520 system with Xuantie C910 cores (RVV0.7 specification) (Built with gcc 14.2.0-ubuntu) (Potentiaily a highway issue)
• SIGSEGV on a SpacemiT-K1 (RVV1.0 but with a 6.1 kernel. Built with gcc 14.2.0-debian)

I have had a build pass SEA tests under qemu on an x64 host, but nowhere near consistently enough to justify not excluding it.

Noting that the The SIGILL/SIGSEGV also occurs in v22.x which doesn't use highway.

I'll add to those results as I get more details.

[sxa]

Noting that the SIGILL goes away on the TH1520 boards with the highway patch referenced in nodejs/build#4099 (comment) however it still gives a SIGSEGV.

[joyeecheung]

Maybe #61167 could make the SIGSEGV go away on RISC-V, though I don't have a board to test it..

[sxa]

Hmmm first attempt with the branch in that PR didn't pass sadly but it'll be interesting to see if it's failing in exactly the same way ...

sxa@bananapif3:~/node$ ./node test/sea/test-single-executable-application.js
Copied /home/sxa/node/out/Release/node to /home/sxa/node/test/.tmp.0/sea
Injected /home/sxa/node/test/.tmp.0/sea-prep.blob into /home/sxa/node/test/.tmp.0/sea
[process 3960824]: --- stderr ---

[process 3960824]: --- stdout ---

[process 3960824]: status = null, signal = SIGSEGV
/home/sxa/node/test/common/child_process.js:112
    throw error;
    ^