-
Notifications
You must be signed in to change notification settings - Fork 211
[AMD] Update MiniMax-M3 FP4 MI355X ATOM image and serving args (0630) #1967
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+17
β6
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π΄ The new perf-changelog entry appended for this PR sets
pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/PLACEHOLDERβ a literal, un-substituted token. The changelog validator (utils/validate_perf_changelog.py) only accepts the canonical/pull/<digits>URL or the sentinelXXX/.../pull/XXX;PLACEHOLDERis neither, soutils/prepare_perf_changelog_merge.pywill raiseappended entry N has unexpected pr-linkand block merge. Replace it with1967(orXXXto hit the auto-canonicalization path).Extended reasoning...
What the bug is. The last entry appended to
perf-changelog.yamlat line 4362 carriespr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/PLACEHOLDER. Every other entry in the file uses either a canonical/pull/<digits>URL (e.g. the immediately preceding/pull/1966) or the accepted sentinelXXX. The literal stringPLACEHOLDERwas never substituted with the real PR number (1967).Why the existing tooling won't accept it.
utils/validate_perf_changelog.pydefines the accepted placeholder set at lines 24-27:validate_added_pr_link()(lines 144-160) rejects any newly-appendedpr-linkthat is neither inPR_LINK_PLACEHOLDERSnor matches the canonicalCANONICAL_PR_LINKregex (which requires\d+, i.e. digits only).PLACEHOLDERmatches neither: it is not the literal stringXXXandPLACEHOLDERis not digits.What triggers the failure.
utils/merge_with_reuse.shinvokesutils/prepare_perf_changelog_merge.pyat lines 181-185 unconditionally in the standard merge flow. That script'scanonicalize_appended_links()(line 112) walks every appended entry and requires eachpr-linkto be either the canonical URL or inPR_LINK_PLACEHOLDERSβ otherwise it raisesChangelogValidationError('appended entry N has unexpected pr-link ...'). The PR-branch validation gate exercises the same code path.Step-by-step proof.
utils/validate_perf_changelog.pyon the diff βvalidate_added_pr_link()seeshttps://github.com/SemiAnalysisAI/InferenceX/pull/PLACEHOLDER.PR_LINK_PLACEHOLDERSβ no match (the sentinel isXXX, notPLACEHOLDER).CANONICAL_PR_LINK.fullmatch()β no match (the regex demands one or more digits after/pull/, andPLACEHOLDERhas none).ChangelogValidationError, the check fails, merge is blocked. The same failure recurs whenprepare_perf_changelog_merge.pyruns during the merge step.Impact. This is a hard merge-blocker: neither the PR-branch validation gate nor the merge-time canonicalize step will accept the entry. Beyond the CI failure, the perf-changelog is an append-only audit log linking each benchmark trigger back to its owning PR; if this were somehow to sneak through, the entry would be orphaned from its PR context forever (per
AGENTS.md, editing in place is discouraged).Fix. Replace
pull/PLACEHOLDERwithpull/1967(the canonical URL for this PR). Alternatively, usepull/XXXβ the merge-prep script will auto-canonicalizeXXXto the real PR number at merge time. The.claude/commands/nuke.mdrecipe uses a bare sentinel tokenPRLINK_PLACEHOLDERthat its script substitutes later; here the substitution never happened, and the sentinel used doesn't match what the validator accepts anyway.