chore(agentic): rerun DSV4 SGLang with standard warmup#2179
Conversation
|
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 关于重新运行失败任务的文档 |
f149e15 to
f9dba8b
Compare
|
Claude finished @cquil11's task in 1m 1s —— View job Review
LGTM - no blocking issues found This is a changelog-only PR (+7 lines in
Note: I couldn't execute |
There was a problem hiding this comment.
LGTM — changelog-only entry documenting a rerun, consistent with the established append pattern in this file.
What was reviewed: confirmed the two config-keys (dsv4-fp4-b200/b300-sglang-agentic-hicache) already exist and were introduced in PR #2112; this entry follows the same append-only changelog convention as other rerun entries (e.g. #2137, #2169) rather than mutating the prior entry. No code, recipe, or config files are touched.
Extended reasoning...
Overview
The diff touches only perf-changelog.yaml, appending a single new changelog entry for two existing config-keys (dsv4-fp4-b200-sglang-agentic-hicache, dsv4-fp4-b300-sglang-agentic-hicache). No recipe scripts, master-config entries, or benchmark code are modified. The entry documents that these configs were rerun with a standardized warmup procedure (regular trajectory warmup + 600s accelerated cache-pressure warmup), per the PR description referencing PR #2112 which originally ran them without the accelerated warmup stage.
Security risks
None. This is a plain-text YAML changelog entry with no executable content, no secrets, and no interaction with auth/crypto/permissions code.
Level of scrutiny
Minimal scrutiny is warranted — this is the same append-only changelog pattern used repeatedly elsewhere in this file (e.g. PR #2137, #2169) for documenting reruns/bumps. I verified the referenced config-keys already exist in the file (introduced by PR #2112) and that this PR adds a new entry rather than editing the prior one, which matches the file's convention of accumulating history rather than mutating past entries.
Other factors
The PR description states the changelog validator (validate_perf_changelog.py) was run and 32 targeted tests passed. No outstanding review comments exist in the timeline beyond the automated recipe-reminder bot message. The bug hunting system found no issues, and there is no logic or code surface here to exercise beyond the YAML format itself.
…ng-agentic-warmup
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29287568103 |
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29289467297 |
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29307996801 |
# Conflicts: # perf-changelog.yaml
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29309990469 |
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=29341333881 |
PR #2112 ran these SGLang agentic configs without the accelerated warmup stage.
This changelog-only PR reruns B200 and B300 with the standard regular warmup followed by the 600-second accelerated warmup.
Tests:
python utils/validate_perf_changelog.py --base-ref origin/main --head-ref HEAD