Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#4,392 4 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@sxa 已经在做这个了。

开始于 2026年7月3日。

评估

这个 Issue 还没有评估数据。

描述

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.

主要语言
Jinja
星标
541
派生
185
平均合并
2 天 19 小时
30 天内合并 PR
6

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nodejs/build 的其他 Issue

查看 nodejs/build 的全部 Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。