Repository navigation
[NV] MiniMax-M3.1-Flash H200 vLLM AgentX update / [NV] MiniMax-M3.1-Flash H200 vLLM AgentX 更新 - #5122
hshrivastava-droid wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Thanks for the contribution!
中文感谢你的贡献!
|
| # MiniMax-M3.1-Flash AgentX on H200: day-zero vLLM image from | ||
| # https://vllm.ai/blog/2026-10-23-minimax-m31-flash, multiarch manifest verified | ||
| # 2026-10-23 (amd64 is minimax-m31-flash-x86_64-cu134). Serve flags follow the | ||
| # MiniMax-M3.1-Flash AgentX on H200: vLLM nightly with FlashInfer SM90 MSA. Serve flags follow the |
There was a problem hiding this comment.
🟡 nit (optional): The rewritten comment is still a config header that names the image, which the AGENTS.md comment rules forbid. The diff rewrote this line instead of dropping it. "vLLM nightly with FlashInfer SM90 MSA" only restates the image: tag two lines below. Fix: delete the header text. If the MSA note is needed, keep it as one short technical line explaining why this image is required, for example FlashInfer SM90 MSA kernels needing fp8 caches.
Why this was flagged
AGENTS.md:56-58 (Comments, mandatory in every file) bans header comments that describe a config and bans comments that restate the code. Its rewrite at nvidia-master.yaml:4156 opens with "MiniMax-M3.1-Flash AgentX on H200: vLLM nightly with FlashInfer SM90 MSA." That text labels the config and repeats the nightly tag set at nvidia-master.yaml:4161. The diff edited this line, so this is new text, not untouched pre-existing text. Nothing breaks at runtime. It only means the PR adds new text against a mandatory repo convention.
Verification: Nothing breaks at runtime. AGENTS.md:56 says "No header comments describing a file, topology, config, recipe, override, or section." The diff deletes the old header lines and replaces them with +# MiniMax-M3.1-Flash AgentX on H200: vLLM nightly with FlashInfer SM90 MSA. Serve flags follow the, directly above minimaxm31flash-fp4-h200-vllm-agentic-dspark:.
|
View unofficial run (performance): https://inferencex.semianalysis.com/inference?unofficialRun=44199027587 View unofficial run (accuracy): https://inferencex.semianalysis.com/evaluation?unofficialRun=44199027587 |
Update the MiniMax-M3.1-Flash FP4 H200 vLLM AgentX config (
minimaxm31flash-fp4-h200-vllm-agentic-dspark).vllm/vllm-openai:nightly-8ca766326652caf4b8e50d1b9118d8a22f6adc73AI model disclosure
PR checklist and change type
Type of Change
Checklist
python -m infx.matrix.changed --base origin/mainlists affected config keys, I have appended one new entry covering them to the physical end ofinferencex-e2e/perf-changelog.yaml; if it lists none, I have added none. I have not edited historical entriesinferencex-e2e/perf-changelog.yamlentry, it carries exactly one primary sweep label:full-sweep-enabled/use <run_id>on this PR中文
更新 MiniMax-M3.1-Flash FP4 H200 vLLM AgentX 配置(
minimaxm31flash-fp4-h200-vllm-agentic-dspark)。镜像同上。🤖 Generated with Claude Code