Skip to content

Update minimaxm2.5-fp4-mi355x-vllm vLLM image to v0.20.2#1319

Closed
functionstackx wants to merge 1 commit into
mainfrom
claude/issue-1154-minimaxm2.5-fp4-mi355x-vllm
Closed

Update minimaxm2.5-fp4-mi355x-vllm vLLM image to v0.20.2#1319
functionstackx wants to merge 1 commit into
mainfrom
claude/issue-1154-minimaxm2.5-fp4-mi355x-vllm

Conversation

@functionstackx
Copy link
Copy Markdown
Contributor

Summary

  • Update minimaxm2.5-fp4-mi355x-vllm image from vllm/vllm-openai-rocm:v0.19.1 to vllm/vllm-openai-rocm:v0.20.2

Ref #1154

Generated with Claude Code

Co-authored-by: Klaud Cold <Klaud-Cold@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Contributor

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

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. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

Comment thread perf-changelog.yaml
- minimaxm2.5-fp4-mi355x-vllm
description:
- "Update vLLM image from v0.19.1 to v0.20.2"
pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX
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.

🟡 The new perf-changelog.yaml entry uses pull/XXX as a placeholder instead of the actual PR number. Since this is PR #1319, the link should be https://github.com/SemiAnalysisAI/InferenceX/pull/1319; as-written it 404s and the changelog row is non-navigable.

Extended reasoning...

What the bug is

The new entry added to perf-changelog.yaml at line 2351 contains a placeholder XXX in its pr-link value:

- config-keys:
    - minimaxm2.5-fp4-mi355x-vllm
  description:
    - "Update vLLM image from v0.19.1 to v0.20.2"
  pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX

This appears to be a template value that was never filled in before submission.

Why this is wrong

Every other entry in perf-changelog.yaml follows the convention of using a real, numeric PR link. The five entries immediately preceding this one all reference real PR numbers (e.g. #1303, #1304, #1305, #1308, #1310). The PR being submitted here is #1319 (per the PR metadata), so the link should read:

  pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/1319

Impact

As-is, the URL https://github.com/SemiAnalysisAI/InferenceX/pull/XXX produces a GitHub 404 when followed, so the new changelog row is non-navigable. Anyone consuming this changelog (humans, dashboards, or downstream automation that resolves these links) won't be able to trace this perf-changelog entry back to the PR that introduced the change. It also breaks the file-wide convention that lets readers cross-reference perf changes with their originating PRs.

Step-by-step proof

  1. The PR metadata above reports <pr number="1319">.
  2. The diff for perf-changelog.yaml adds exactly one entry whose pr-link is https://github.com/SemiAnalysisAI/InferenceX/pull/XXX.
  3. Resolving that URL: GitHub has no pull request with id XXX (non-numeric), so any client following the link gets a 404.
  4. Substituting the real PR number gives https://github.com/SemiAnalysisAI/InferenceX/pull/1319, which is the canonical link for this PR and matches the format used by all prior entries in the file.

How to fix

Replace pull/XXX with pull/1319 on line 2351 of perf-changelog.yaml. No other changes needed.

@Oseltamivir Oseltamivir deleted the claude/issue-1154-minimaxm2.5-fp4-mi355x-vllm branch May 12, 2026 21:02
@github-actions
Copy link
Copy Markdown
Contributor

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

Projects

Development

Successfully merging this pull request may close these issues.

2 participants