-
Notifications
You must be signed in to change notification settings - Fork 159
dsv4-fp8-h200-vllm-mtp: bump num_speculative_tokens 1 → 2 #1279
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
+9
−2
Merged
Changes from all commits
Commits
Show all changes
2 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
Oops, something went wrong.
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.yamlentry for this PR haspr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/PLACEHOLDERon line 2216 — the seed placeholder from the AGENTS.md template was never replaced with the real PR number (1279). Clicking through the changelog entry to find the originating PR returns a GitHub 404, defeating the audit-trail purpose of the file. Trivial one-token fix on line 2216:PLACEHOLDER→1279.Extended reasoning...
What the bug is
The new entry appended to
perf-changelog.yamlfor thedsv4-fp8-h200-vllm-mtpsweep ends with:The rendered diff text in the GitHub UI happens to show
pull/1279, but the actual committed content atHEAD(026143c) on line 2216 still saysPLACEHOLDER.tail -1 perf-changelog.yamlandgit show HEAD -- perf-changelog.yaml | tail -1both confirm this directly.Why the placeholder is there
AGENTS.md(around lines 281 and 304) instructs authors to seed new changelog entries withpull/XXX-style placeholder text and substitute the real PR number after pushing. The author of this PR followed the template but skipped the substitution step.Why nothing caught it
utils/matrix_logic/validation.py:483declarespr_linkas a plainstr, with no URL/format/regex constraint:So
PLACEHOLDERvalidates fine. There is no other test or lint that would have rejected it.How rare this is
This is the only non-numeric
pr-linkin the entire 252-entry file:Every other one of the ~250 entries points at a real numeric PR.
Step-by-step proof
perf-changelog.yamlatHEADafter this PR merges.dsv4-fp8-h200-vllm-mtpsweep [NVIDIA] Add TRT 70B (FP8 and FP4) #2.pr-linkto find the PR that introduced this sweep.https://github.com/SemiAnalysisAI/InferenceX/pull/PLACEHOLDER.PLACEHOLDERis not a numeric PR id.Impact
Not a runtime/behavior bug — the benchmark recipe itself is untouched. But the changelog entry is broken-as-merged: the audit-trail link 404s, and the entry sits next to ~250 well-formed siblings as the lone outlier. Easy to miss once it lands on
main.Fix
One-token edit on line 2216 of
perf-changelog.yaml:(Optional follow-up, out of scope for this PR: tighten
pr_linkinutils/matrix_logic/validation.py:483to require a numeric PR id, e.g.pydantic.HttpUrl+ a regex check or a custom validator that asserts the path ends with/pull/<int>. That would prevent the same template-substitution miss from sneaking past in the future.)