Skip to content

ci: 增加自建 runner 可用性探测 - #138

Open
licy666 wants to merge 2 commits into
Ascend:mainfrom
licy666:ci/probe-self-hosted-runners
Open

ci: 增加自建 runner 可用性探测#138
licy666 wants to merge 2 commits into
Ascend:mainfrom
licy666:ci/probe-self-hosted-runners

Conversation

@licy666

@licy666 licy666 commented Aug 26, 2026

Copy link
Copy Markdown

摘要

  • 新增一条只支持手动触发(workflow_dispatch)的探测流水线,覆盖 A2 / A3 各档卡数的 runner 标签。
  • a2 / a3 是机器型号(A2 = 910B,A3 = 910C);标签尾部数字是该档 scale set 可用的卡数。
  • 每个 job 拉取对应芯片系列的 AscendHub CANN 镜像,运行 npu-smi info,并检查容器里至少能看到与标签尾部数字相同数量的 NPU 设备节点。
  • .github/actionlint.yaml 里登记这些 runner 标签,避免 actionlint 把它们当成未知标签。

覆盖的标签:

型号 1 卡 2 卡 4 卡 8 卡 16 卡
A2 linux-aarch64-a2-1 linux-aarch64-a2-2 linux-aarch64-a2-4 linux-aarch64-a2-8 linux-aarch64-a2-16
A3 linux-aarch64-a3-1 linux-aarch64-a3-2 linux-aarch64-a3-4 linux-aarch64-a3-8 linux-aarch64-a3-16

这是探测流水线,不是文档构建。某个 job 一直停在排队(Queued),说明这个仓还没有对应的 scale set,或当时没有空闲容量。job 变绿且日志里有 npu-smi 输出、设备节点数达到标签要求,说明该标签能在本仓接活。

fail-fast: false:一档失败不会取消其他档,两边可以分别看。定时任务(schedule)保持注释,避免合入后按点占 NPU。

测试计划

  • 合入 main(或确认 workflow 文件已在默认分支上),然后在 Actions 页运行 Probe self-hosted runners,或使用 gh workflow run
  • 确认上表 10 个标签各自被接走,且 npu-smi 列出的卡数不少于标签尾部数字。
  • 若某个 job 一直排队,把该标签视为对 Ascend/docs 尚不可用。

Dispatch a job against linux-aarch64-a2-2 and linux-aarch64-a3-2 so we
can see whether those labels can pick up work for this repo.
@ascend-robot

Copy link
Copy Markdown

CLA Signature Pass

licy666, thanks for your pull request. All authors of the commits have signed the CLA. 👍

@licy666 licy666 changed the title ci: add self-hosted runner availability probe ci: 增加自建 runner 可用性探测 Aug 26, 2026
Cover linux-aarch64-{a2,a3}-{1,2,4,8,16} and check that each label
exposes the number of NPU devices in its suffix.
@ascend-robot

Copy link
Copy Markdown

CLA Signature Pass

licy666, thanks for your pull request. All authors of the commits have signed the CLA. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants