Single Executable Application tests often fail on RISC-V
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Single Executable Application (SEA) tests and reproduce them on the reported RISC-V hardware or under qemu, comparing the SIGILL and SIGSEGV results across Node v25.2.2 and v22.x. Done requires establishing the affected configurations and determining whether the SEA tests need a RISC-V exclusion or another documented handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux, nodejs
- Domain
- build-system, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100