Repository navigation
Single Executable Application tests often fail on RISC-V #61110
Description
Activity
- addedriscv64Issues and PRs related to the 64-bit RISC-V architecture.Issues and PRs related to the 64-bit RISC-V architecture.
on Dec 18, 2025 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.
Maybe #61167 could make the SIGSEGV go away on RISC-V, though I don't have a board to test it..
Reacted by Stewart X AddisonHmmm 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; ^- addedsingle-executableIssues and PRs related to single-executable applications.Issues and PRs related to single-executable applications.
on Dec 30, 2025 hmm, well I guess at least when #61167 lands it would be easier to debug and find out why instead of jumping through a WASM blob to debug..
Reacted by Stewart X Addisongithub-actions commented
on Jul 20, 2026 on Jul 20, 2026 – with GitHub ActionsContributorMore actionsThis issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jul 20, 2026 Still valid I believe, although it possibly requires retesting with the latest builds.
- removedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jul 21, 2026 This may be related to nodejs/build#4433 (comment) and #65564
- added a commit that references this issue
on Aug 28, 2026 - added 2 commits that reference this issue
on Aug 29, 2026 - added a commit that references this issue
on Sep 9, 2026 - added 2 commits that reference this issue
on Sep 9, 2026
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:
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.