Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Evaluate feasibility of RISC-V SpacemiT-K3 systems for CI testing

Abierto
#4,392 4 comentarios 0 reacciones 1 asignado Ver en GitHub

@sxa ya está trabajando en esto.

Desde el 3/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

platform:riscv64

Most of the RISC-V systems we've been able to add into the jenkins CI have been too slow to put into the main node-test-commit runs.
While this could have been mitigated if we take the "fanned" approach as we have for other platforms that is not ideal.

There are newer boards based on the SpacemiT-K3 SoC which are starting to become available and I have acquired one today with a view to evaluating the performance. Initial tests suggest it can build Node.js in around 3h with an unpopulated ccache which puts it in line with some of our other platforms meaning that it would not unduly delay PR testing if we were to integrate such systems into the PR testing process.

Scaleway are looking at having K3 based servers in the near future to supplement the existing slower TH1520 boards that they have available, so it is likely that we would be able to obtain capacity along the lines of what I'm currently testing. Based on other testing I've done the K3 boards can do things around 4-5 times faster than the TH1520 ones in many scenarios (even excluding the use of the eight additional slower A100 cores on the board)

Adding it to the CI would be conditional on it being able to run cleanly, and while my initial runs have shown some unexpected issues/crashes I will work through some of those in this issue and https://github.com/nodejs/build/issues/4099 for any other issues related to getting to green on this platform.

Lenguaje dominante
Jinja
Estrellas
541
Forks
185
Merge medio
2 d 18 h
PR fusionados (30 d)
6

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nodejs/build

Todos los issues de nodejs/build

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.