Skip to content

Single Executable Application tests often fail on RISC-V #61110

Description

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

Activity

  1. added
    riscv64Issues and PRs related to the 64-bit RISC-V architecture.
    on Dec 18, 2025
  2. sxa commented on Dec 21, 2025

    @sxa
    MemberAuthor

    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.

  3. joyeecheung commented on Dec 24, 2025

    @joyeecheung
    Member

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

  4. sxa commented on Dec 30, 2025

    @sxa
    MemberAuthor

    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;
        ^
    
  5. joyeecheung commented on Jan 5, 2026

    @joyeecheung
    Member

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

  6. github-actions commented on Jul 20, 2026

    @github-actions
    Contributor

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

  7. added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jul 20, 2026
  8. sxa commented on Jul 20, 2026

    @sxa
    MemberAuthor

    Still valid I believe, although it possibly requires retesting with the latest builds.

  9. removed
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jul 21, 2026
  10. MikeMcC399 commented on Aug 26, 2026

    @MikeMcC399
    Contributor

    This may be related to nodejs/build#4433 (comment) and #65564

  11. added a commit that references this issue on Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    riscv64Issues and PRs related to the 64-bit RISC-V architecture.single-executableIssues and PRs related to single-executable applications.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions