[Klaud Cold] Update qwen3.5-fp8-gb300-dynamo-sglang-mtp SGLang image to v0.5.19-cu130 / 将 qwen3.5-fp8-gb300-dynamo-sglang-mtp 的 SGLang 镜像更新至 v0.5.19-cu130 - #3064
Conversation
Bump qwen3.5-fp8-gb300-dynamo-sglang-mtp and its seven referenced srt-slurm recipes from lmsysorg/sglang:v0.5.14-cu130 to the digest-pinned lmsysorg/sglang:v0.5.19-cu130 release manifest list. 将 qwen3.5-fp8-gb300-dynamo-sglang-mtp 及其引用的七个 srt-slurm 配方镜像从 lmsysorg/sglang:v0.5.14-cu130 更新为按摘要固定的 lmsysorg/sglang:v0.5.19-cu130 发布版本。 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
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 For PR verification, add the 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 模板,包括保留英文语句 如需进行 PR 验证,请为此 PR 添加 PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档 |
|
Baseline: 2026-07-30 · Mean latency
Note: All rows: unavailable.
中文**基线:**2026-07-30 · |
|
Compatibility check · incompatible · no GPU dispatch · 2026-09-13T00:51:17Z Finding
Next: A maintainer retargets the family's Dynamo pin ( 中文兼容性检查 · 不兼容 · 未调度 GPU · 2026-09-13T00:51:17Z **发现:**SGLang #36681(提交 **下一步:**由维护者将该配置族的 Dynamo 固定版本(七个配方的 |
|
incompatible · Cleanup pending. Stop and confirm owned runs before closing. 中文incompatible · 清理待完成。先停止并确认自有运行结束,再关闭 PR。 |
|
incompatible · Repairs: 0 · Runs: — 中文incompatible · 修复次数:0 · 运行:— |
Goal: Update SGLang image from
lmsysorg/sglang:v0.5.14-cu130@sha256:5027e95bf6ec536856b1b52a91d1f35ff5c564ab83e8a94758a169ff09bb8df3tolmsysorg/sglang:v0.5.19-cu130@sha256:d6e7288627be8b02be88e4bba38e73f6d50e2826869f753c13a4c4385ab3eda9.Baseline: 2026-07-30 ·
lmsysorg/sglang:v0.5.14-cu130@sha256:5027e95bf6ec536856b1b52a91d1f35ff5c564ab83e8a94758a169ff09bb8df3Mean latency · Sources: API 1, API 2, API 3
Note: All rows: unavailable.
中文
**目标:**将 SGLang 镜像从
lmsysorg/sglang:v0.5.14-cu130@sha256:5027e95bf6ec536856b1b52a91d1f35ff5c564ab83e8a94758a169ff09bb8df3更新为lmsysorg/sglang:v0.5.19-cu130@sha256:d6e7288627be8b02be88e4bba38e73f6d50e2826869f753c13a4c4385ab3eda9。**基线:**2026-07-30 ·
lmsysorg/sglang:v0.5.14-cu130@sha256:5027e95bf6ec536856b1b52a91d1f35ff5c564ab83e8a94758a169ff09bb8df3平均延迟 · 来源: API 1, API 2, API 3;数值及异常说明见上表。