[Klaud Cold] Update kimik2.5-int4-b300-vllm vLLM image to v0.24.0 / 将 kimik2.5-int4-b300-vllm 的 vLLM 镜像 升级至 v0.24.0

[functionstackx]

Summary

Update vLLM image from vllm/vllm-openai:v0.21.0 to vllm/vllm-openai:v0.24.0

Recipes touched: kimik2.5-int4-b300-vllm

中文说明

将 vLLM 镜像 从 vllm/vllm-openai:v0.21.0 升级至 vllm/vllm-openai:v0.24.0。涉及配置：kimik2.5-int4-b300-vllm。

Test plan

• full-sweep-fail-fast sweep passes.

🤖 Generated with Claude Code

[github-actions]

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-enabled or full-sweep-fail-fast label to this PR — the benchmark sweep only runs on labeled PRs.

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-enabled 或 full-sweep-fail-fast 标签 — 基准测试 sweep 仅在带有标签的 PR 上运行。

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

[claude]

LGTM — mechanical vLLM image bump for kimik2.5-int4-b300-vllm with matching perf-changelog entry.

Extended reasoning...

Overview

This PR bumps the vLLM image tag for the kimik2.5-int4-b300-vllm recipe in configs/nvidia-master.yaml from v0.21.0 to v0.24.0, and adds a corresponding entry in perf-changelog.yaml. Scope is limited to two lines of YAML config.

Security risks

None. This is a container image tag change on a benchmark recipe config; no auth, crypto, or permission surfaces are touched. The image continues to be pulled from the same upstream vllm/vllm-openai repository.

Level of scrutiny

Low. This is a routine [Klaud Cold] image-bump PR following the established nuke pattern, gated by the full-sweep-fail-fast label so CI will exercise the recipe end-to-end before merge. The bug hunting system reported no issues.

Other factors

The diff is exactly what the description claims — a single image-tag change plus a matching changelog entry. Nothing here requires human judgment beyond letting the sweep validate the new image.

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=28720095124
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=28720095124

[functionstackx]

/reuse-sweep-run