Skip to content

[Klaud Cold] Update qwen3.5-fp8-b300-sglang-agentic-mtp SGLang image to nightly-dev-cu13-20260907-30705c00 and move to cluster:b300-dsxe - #2881

Open
functionstackx wants to merge 1 commit into
mainfrom
klaud-cold/qwen3.5-fp8-b300-sglang-agentic-mtp-nightly-dev-cu13-20260907-30705c00
Open

[Klaud Cold] Update qwen3.5-fp8-b300-sglang-agentic-mtp SGLang image to nightly-dev-cu13-20260907-30705c00 and move to cluster:b300-dsxe#2881
functionstackx wants to merge 1 commit into
mainfrom
klaud-cold/qwen3.5-fp8-b300-sglang-agentic-mtp-nightly-dev-cu13-20260907-30705c00

Conversation

@functionstackx

@functionstackx functionstackx commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

Update the SGLang image for qwen3.5-fp8-b300-sglang-agentic-mtp from lmsysorg/sglang:v0.5.16-cu130 to lmsysorg/sglang:nightly-dev-cu13-20260907-30705c00, and move the recipe from the retired cluster:b300-nv runner to cluster:b300-dsxe.

Recipes touched: qwen3.5-fp8-b300-sglang-agentic-mtp

Test plan

  • full-sweep-enabled sweep passes on cluster:b300-dsxe.

🤖 Generated with Claude Code


Note

Low Risk
Benchmark recipe and changelog only; no application runtime or security paths. Main operational note is non-comparable perf history across the fleet move.

Overview
Updates qwen3.5-fp8-b300-sglang-agentic-mtp in nvidia-master.yaml: SGLang moves from v0.5.16-cu130 to nightly-dev-cu13-20260907-30705c00 (aligned with other Qwen3.5 SGLang AgentX image bumps), and the runner switches from retired cluster:b300-nv to cluster:b300-dsxe so sweeps can schedule again.

Adds a matching perf-changelog.yaml entry noting unchanged TP/EP grids and script settings, that qwen3.5-fp8-b300-sglang-agentic-power-ab stays pinned for cross-precision parity, and that the runner change forces a full curve rerun on DSXE (not append-only).

Reviewed by Cursor Bugbot for commit 847e9dd. Bugbot is set up for automated code reviews on this repo. Configure here.

…to nightly-dev-cu13-20260907-30705c00 and move to cluster:b300-dsxe

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@functionstackx
functionstackx force-pushed the klaud-cold/qwen3.5-fp8-b300-sglang-agentic-mtp-nightly-dev-cu13-20260907-30705c00 branch from de9c9ce to 847e9dd Compare September 8, 2026 01:41
@github-actions

github-actions Bot commented Sep 8, 2026

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

github-actions Bot commented Sep 8, 2026

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 关于重新运行失败任务的文档

@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.

I reviewed this PR and found no bugs. Because the runner change means the whole AgentX curve reruns on the newly added cluster:b300-dsxe fleet rather than an append-only bump, a human look at the results would still be worthwhile.

  • Confirmed cluster:b300-nv's labels were already dropped and cluster:b300-dsxe exists in configs/runners.yaml (#2826), matching the retirement claim.
  • perf-changelog.yaml appends correctly at the tail with the right config-keys/scenario-type shape.
  • pr-link is still the literal placeholder string, not yet the real PR URL the changelog gate requires.
  • Could not confirm from this branch that the sibling B200/H200/H100 Qwen3.5 SGLang AgentX-mtp recipes are already on the claimed nightly-dev-cu13-20260907-30705c00 tag; they still show v0.5.16-cu130 (or an older nightly for the H200 hicache variant) in nvidia-master.yaml here.
Extended reasoning...

Overview

The diff touches exactly two files: configs/nvidia-master.yaml (bumps the qwen3.5-fp8-b300-sglang-agentic-mtp recipe's SGLang image tag and moves its runner from the retired cluster:b300-nv to cluster:b300-dsxe) and perf-changelog.yaml (a single tail-appended entry documenting both changes). No source code, workflow logic, or security-sensitive paths are touched — this is a pure recipe/config edit.

Security risks

None. No secrets, auth, or code-execution paths are touched; this is a YAML data change consumed by the existing sweep/validation tooling.

Level of scrutiny

Low-to-moderate. The change is small and mechanical (image tag + runner label + changelog entry), matching the repo's well-established "Klaud Cold" image-bump pattern. However, two things push this past a rubber-stamp approval: (1) the runner change is explicitly non-append-only per the changelog text itself — the entire curve reruns on cluster:b300-dsxe, a fleet added only days ago (commit ee8f457, #2826) — so there is real behavioral risk beyond a typical append-only point addition; (2) the changelog's pr-link is still a literal placeholder rather than a real PR URL, which is expected to be self-corrected by the standard Klaud Cold post-PR-create amend step but is nonetheless an open item at the time of this review.

Other factors

I independently verified: cluster:b300-dsxe exists in configs/runners.yaml and cluster:b300-nv's runner labels were already removed in #2826 (12 other recipes in nvidia-master.yaml are still pinned to the now-labelless cluster:b300-nv, which commit ee8f457's own message acknowledges as a known, separately-tracked issue — not something this PR needs to fix). I also spot-checked the changelog's claim that sibling B200/H200/H100 Qwen3.5 SGLang AgentX-mtp recipes already moved to nightly-dev-cu13-20260907-30705c00: in this branch's snapshot of nvidia-master.yaml, qwen3.5-fp8-b200-sglang-agentic-mtp, qwen3.5-fp4-b200-sglang-agentic-mtp, qwen3.5-fp8-h200-sglang-agentic-mtp, and qwen3.5-fp8-h100-sglang-agentic-mtp are still on lmsysorg/sglang:v0.5.16-cu130, and qwen3.5-fp8-h200-sglang-agentic-hicache-mtp is on a different, older nightly (nightly-dev-cu13-20260815-a5ba081f). This could simply reflect that PRs #2861/#2862/#2868/#2869 haven't landed in this local checkout yet, but I could not confirm that from the available history, so I'm flagging it as something worth a human's attention rather than treating it as a confirmed defect (it echoes a candidate issue an earlier investigation round already looked at and ruled out). No bugs were reported by the automated hunt, and the change is small enough that I lean toward defer rather than a blocking finding, but the non-append-only runner move plus the open pr-link placeholder are enough that I don't have the high confidence required to approve outright.

This review covers commit de9c9ce, which is no longer the latest commit on this pull request; later commits are not covered by it.

@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

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

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant