Skip to content

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

Open
functionstackx wants to merge 1 commit into
mainfrom
klaud-cold/kimik2.5-int4-mi355x-vllm-v0.24.0
Open

[Klaud Cold] Update kimik2.5-int4-mi355x-vllm vLLM ROCm image to v0.24.0 / 将 kimik2.5-int4-mi355x-vllm 的 vLLM ROCm 镜像 升级至 v0.24.0#2077
functionstackx wants to merge 1 commit into
mainfrom
klaud-cold/kimik2.5-int4-mi355x-vllm-v0.24.0

Conversation

@functionstackx

Copy link
Copy Markdown
Collaborator

Summary

Update vLLM ROCm image from vllm/vllm-openai-rocm:nightly-b8336c3c7c298e0878f22a7bf70f4e295b2f4e01 to vllm/vllm-openai-rocm:v0.24.0

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

中文说明

将 vLLM ROCm 镜像 从 vllm/vllm-openai-rocm:nightly-b8336c3c7c298e0878f22a7bf70f4e295b2f4e01 升级至 vllm/vllm-openai-rocm:v0.24.0。涉及配置:kimik2.5-int4-mi355x-vllm

Test plan

  • full-sweep-fail-fast sweep passes.

🤖 Generated with Claude Code

中文:将 kimik2.5-int4-mi355x-vllm 的 vLLM ROCm 镜像 升级至 v0.24.0。

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@functionstackx functionstackx requested a review from 1am9trash as a code owner July 4, 2026 21:24
@functionstackx functionstackx force-pushed the klaud-cold/kimik2.5-int4-mi355x-vllm-v0.24.0 branch from f362c0b to b5fb27f Compare July 4, 2026 21:24
@github-actions

github-actions Bot commented Jul 4, 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-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-enabledfull-sweep-fail-fast 标签 — 基准测试 sweep 仅在带有标签的 PR 上运行。

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.

LGTM — mechanical image tag bump (nightly → v0.24.0) for a single vLLM recipe with matching perf-changelog entry.

Extended reasoning...

Overview

This PR bumps the vLLM ROCm image for the kimik2.5-int4-mi355x-vllm recipe from a pinned nightly (nightly-b8336c3c7c298e0878f22a7bf70f4e295b2f4e01) to the stable v0.24.0 tag, and appends a matching entry to perf-changelog.yaml. Two files, two edits, single recipe affected.

Security risks

None. This is a benchmark-config-only change — no auth, crypto, permissions, or execution-path logic is touched. The new image tag comes from the same vllm/vllm-openai-rocm repository already used across many recipes in this file.

Level of scrutiny

Low. This matches the standard [Klaud Cold] image-bump pattern seen across the repo (e.g. #1980 in the diff context). The full-sweep-fail-fast label is already applied, so correctness will be validated by the benchmark sweep before merge.

Other factors

The perf-changelog entry follows the established schema (config-keys, description, pr-link) and correctly targets only the modified recipe. No bugs were flagged by the bug-hunting system.

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