Skip to content

[AMD] exclude mia1-p01-g09 from AMD multi-node Slurm jobs#2283

Open
seungrokj wants to merge 2 commits into
mainfrom
amd/server_list
Open

[AMD] exclude mia1-p01-g09 from AMD multi-node Slurm jobs#2283
seungrokj wants to merge 2 commits into
mainfrom
amd/server_list

Conversation

@seungrokj

@seungrokj seungrokj commented Jul 19, 2026

Copy link
Copy Markdown
Collaborator

Evidence of failing PD on these nodes
https://github.com/SemiAnalysisAI/InferenceX/actions/runs/29683845216/job/88211152187?pr=2247

Summary

  • Add mia1-p01-g09 and mia1-p01-g14 to the default SLURM_EXCLUDE_NODES list in the AMD multi-node submit script

Test plan

  • Verify multi-node AMD Slurm jobs no longer schedule on the excluded nodes

🤖 Generated with Claude Code

…jobs

Add two additional problematic nodes to the default SLURM_EXCLUDE_NODES
list in the AMD multi-node submit script.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

@seungrokj seungrokj changed the title fix: exclude mia1-p01-g09 and mia1-p01-g14 from AMD multi-node Slurm jobs [AMD] exclude mia1-p01-g09 and mia1-p01-g14 from AMD multi-node Slurm jobs Jul 19, 2026
@seungrokj

Copy link
Copy Markdown
Collaborator Author

cc. @hongxiayang

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — trivial, mechanical change (adding two hostnames to a default exclude list); the one finding is a repo-wide PR-metadata nit unrelated to the code correctness.

Extended reasoning...

Overview

Single-line change to benchmarks/multi_node/amd_utils/submit.sh: appends mia1-p01-g09 and mia1-p01-g14 to the default value of SLURM_EXCLUDE_NODES (a comma-separated string used to build the --exclude sbatch argument). This only changes the default — any caller that already sets SLURM_EXCLUDE_NODES in the environment is unaffected, and the mechanism for consuming the list (splitting on commas into --exclude) is unchanged.

Security risks

None. This is a benchmarking/ops script that composes a Slurm sbatch exclude list; there is no user input, auth, or secret handling involved.

Level of scrutiny

Low. This is a one-line data change (extending a hostname list) in a non-critical benchmark orchestration script, following the exact existing pattern (comma-separated hostnames already excluded for the same reason — broken Docker sockets). No control-flow or logic changes.

Other factors

The only finding from the bug-hunting pass is a nit that the PR title/description lacks the repo-mandated Chinese translation section — this is a metadata/process issue, not a code defect, and doesn't bear on correctness of the fix. The reviewed candidate issue about leaving other documented bad nodes (g19/g31/g37) unexcluded was already ruled out by the verifier pass as out of scope for this fix. Given the change is small, self-contained, and mechanical, I'm approving despite the nit.

Comment on lines 166 to 172
# Optional: exclude specific nodes (e.g. nodes with broken Docker sockets).
# Set SLURM_EXCLUDE_NODES env var to a comma-separated list of hostnames.
EXCLUDE_OPT=()
SLURM_EXCLUDE_NODES="${SLURM_EXCLUDE_NODES:-mia1-p01-g11,mia1-p01-g12,mia1-p01-g15}"
SLURM_EXCLUDE_NODES="${SLURM_EXCLUDE_NODES:-mia1-p01-g11,mia1-p01-g12,mia1-p01-g15,mia1-p01-g09,mia1-p01-g14}"
if [[ -n "${SLURM_EXCLUDE_NODES:-}" ]]; then
EXCLUDE_OPT=(--exclude "$SLURM_EXCLUDE_NODES")
fi

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 This PR's title and description are English-only, but AGENTS.md mandates bilingual PR titles/descriptions (<English> / <中文标题> format plus a ## 中文说明 section). This is a pre-existing, repo-mandated documentation requirement unrelated to the actual code fix, which is correct.

Extended reasoning...

AGENTS.md (line 7) explicitly states: "PR and GitHub-issue titles & descriptions must be bilingual — include a Simplified Chinese version in addition to English. Title format: <English title> / <中文标题>. In the PR/issue body, follow the English content with its Chinese translation (e.g. a ## 中文说明 section mirroring the summary...)." This applies to every PR and every issue in the repository, per that same section.

This PR's title is "fix: exclude mia1-p01-g09 and mia1-p01-g14 from AMD multi-node Slurm jobs" — English only, with no / <中文标题> suffix. The PR body contains only ## Summary and ## Test plan sections in English; there is no accompanying ## 中文说明 section translating the summary into Simplified Chinese. Both requirements from AGENTS.md are unmet.

This is not a subjective style nit invented by the reviewer — it's an explicit, verifiable, repo-mandated checklist item that applies uniformly to all PRs, independent of the code change itself. The underlying code fix (adding mia1-p01-g09 and mia1-p01-g14 to the default SLURM_EXCLUDE_NODES list on line 169 of benchmarks/multi_node/amd_utils/submit.sh) is correct and not in question — the issue is purely with the PR metadata that accompanies it.

Step-by-step proof:

  1. Open AGENTS.md and read the callout on line 7: it requires <English title> / <中文标题> for the title, and a ## 中文说明 section (or equivalent trailing Chinese paragraph) in the body.
  2. Read this PR's actual title: "fix: exclude mia1-p01-g09 and mia1-p01-g14 from AMD multi-node Slurm jobs" — no / <中文标题> segment is present.
  3. Read this PR's actual body: it contains ## Summary (English bullet) and ## Test plan (English checklist) only — no ## 中文说明 or any Chinese text anywhere.
  4. Therefore the PR fails both the title-format and body-translation requirements mandated by AGENTS.md.

Impact and fix: There's no runtime or functional impact — the code change itself (excluding the two broken nodes from Slurm scheduling) is unaffected and correct. The fix is simply for the PR author to append / <中文标题> to the title (e.g. "fix: exclude mia1-p01-g09 and mia1-p01-g14 from AMD multi-node Slurm jobs / 修复:在 AMD 多节点 Slurm 任务中排除 mia1-p01-g09 和 mia1-p01-g14") and add a ## 中文说明 section mirroring the Summary/Test plan in Simplified Chinese before merging.

@hongxiayang hongxiayang left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@seungrokj seungrokj changed the title [AMD] exclude mia1-p01-g09 and mia1-p01-g14 from AMD multi-node Slurm jobs [AMD] exclude mia1-p01-g09 from AMD multi-node Slurm jobs Jul 20, 2026
Node mia1-p01-g14 is healthy again, remove it from the default
exclude list to expand the available runner pool.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants