Repository navigation
Conversation
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 19, 2026 22:32
492e702 to
49c2673
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 19, 2026 22:32
1ebcec9 to
d860fa9
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 19, 2026 22:46
49c2673 to
afca1f6
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 19, 2026 22:46
d860fa9 to
5399ccd
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 19, 2026 22:50
afca1f6 to
e9900fc
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 19, 2026 22:50
5399ccd to
ae7a1a2
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 19, 2026 23:10
e9900fc to
3efc777
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 19, 2026 23:11
ae7a1a2 to
72624f0
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 20, 2026 05:25
3efc777 to
49dcd67
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 20, 2026 05:25
72624f0 to
95a9f1d
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 20, 2026 05:59
49dcd67 to
38e317f
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 20, 2026 05:59
95a9f1d to
551eb09
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 20, 2026 06:02
38e317f to
cd8a086
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 20, 2026 06:02
551eb09 to
9ebdbc5
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 20, 2026 06:13
cd8a086 to
62d113d
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 20, 2026 06:13
9ebdbc5 to
d9ff36c
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 20, 2026 06:21
62d113d to
835b8a1
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
2 times, most recently
from
October 20, 2026 07:55
536d56b to
4876d5d
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 20, 2026 08:23
835b8a1 to
846bf1d
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
October 20, 2026 08:23
4876d5d to
04d94f0
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 21, 2026 02:30
846bf1d to
e14c4b0
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
2 times, most recently
from
October 21, 2026 03:19
a60a651 to
fc86036
Compare
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
October 21, 2026 08:47
e14c4b0 to
c87ab20
Compare
…nd mstar-only request_extra), and --skip ROW/ARM[/WORKLOAD] for arms a dry run failed
… config; run_row checks skips only when there are some
…, and one still running after 30 min ends the arm
…rms' scores in place
… after mstar on each omni row
…h SGLang Diffusion needs
…ty exact matches and divergence sums for Qwen3-Omni
…ngines', not its FLUX.2 JPEG default
…nd moves up when taken, and SGLang Diffusion's master and scheduler ports follow it
…s port leaves nothing out
…ose cell got nothing back ends there
…nditioning crop, right after mstar in the video table
… first frames to every engine
… and crops them itself
Row.i2v_own_frames_arms had no other user. The Cosmos3 i2v correctness family no longer asks for the conditioning_resize override.
Older result files keep the previous marker name and are still filtered.
On a node where SLURM hands a job some GPUs in ROCR_VISIBLE_DEVICES with no device cgroup, amd-smi lists every GPU, so HIP 0 was read as the node's first GPU (health checks, occupancy, NUMA binding).
Jobs that share a node and its /tmp each see their GPU as HIP 0, so a lock named by HIP index kept the second job off a GPU nobody else had.
merceod
force-pushed
the
users/atindra/pr-10b-docs
branch
from
November 1, 2026 07:49
99d4ad5 to
e490e7b
Compare
merceod
force-pushed
the
users/atindra/pr-11-harnesses
branch
from
November 1, 2026 07:49
406bd6e to
a92a33c
Compare
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Stacked on #691, the second docs PR. Needs #688 (media) for its loaders (
benchmark/dataset.pyand the Omni correctness family importmedia_io). Nothing undermstar/changes.Correctness runner (
benchmark/correctness/). Serves one config, sends a fixed sample set, scores the outputs against a reference (transformers, diffusers or the model's own package) and writes a verdict per model family.AMD tables (
benchmark/amd/). Launches competitor arms (vLLM, vLLM with AITER, SGLang, vllm-omni, sglang-omni, SGLang Diffusion) from pinned containers with cited recipes, gates each arm on node health, runs warmup plus 3 runs and writes tables with versions, the attention backend each engine picked, the fused-MoE configs each server loaded, co-tenants and a correctness column. GPU numbering follows HIP (amd-smi's order differs on 8-GPU nodes, so it's mapped by PCI address), busy GPUs are found by memory in use, and TP rows run gloo on loopback.long_prompt.pyruns worker_phases for concurrent ~1k-token prompts against any serving config. A row can name a different mstar deployment config per arm, so the Qwen3-TTS 1.7B row runsmstaronqwen3tts_1p7b_split_bf16and anmstar-colocatedarm onqwen3tts_1p7b, and the table shows which config each engine column used.Smaller changes.
benchmark.runnergains vLLM and SGLang text clients, sample-set prompts, unique prompt tags, ITL and token counts in results.json. GPU memory queries take amd-smi too, in the Wan2.2 and Waypoint harnesses and the benchmarking skill'sserver.sh. The Kokoro ONNX baselines take the MIGraphX and ROCm execution providers and refuse a missing one. No more /scratch prompt-file defaults.run_benchmark.shloses two unbound variables.NVIDIA: nothing under
mstar/changes. The runner and the vLLM/SGLang clients work against any server.Tests
ruff check .test_correctness_metrics.py,test_correctness_runner.py,test_amd_bench.py(new), plustest_bench_summary.py,test_video_frame_protocol.py,test_psnr_tool.pytest/modular,test/distributedandtest/sampling_teston an MI300X node with GPUs hidden, on the integration branch that carries this whole stack, rebased on maintest/rusttheretest/rocmon MI300X, same branchtest/modularonly fails the twotest_dump_stacksenvironment cases main fails too (7174 passed before the last three test fixes, targeted rerun on the tip 398 passed), other CPU suites 248 passed, TP lockstep sim 7 passed,test/rust368 passed. One MI300X:test/rocm675 passed, fused-MoE and sampler GPU tests 228 passed, served smoke rows for Qwen3.5 0.8B, Kokoro, Whisper large-v3 and Cosmos3 DROID match the earlier runsWhat the runner has found so far on MI300X and MI325X (all with the rest of this stack). Pass: Qwen3.5 0.8B-9B (text and image), Whisper, Orpheus, Kokoro, Qwen3-TTS 0.6B, Chatterbox, OmniVoice, Qwen3-Omni media and speech, the Cosmos3 DROID and action configs, Cosmos3 nano t2v, V-JEPA2-AC, Wan2.2. Pass with a caveat: Qwen3-TTS 1.7B and Chatterbox multilingual (sampled, the extra errors are proper nouns or reference artifacts), and Qwen3-Omni's cold start, which is over the runner's 2400 s limit without a saved MIOpen database. Fail: pi05 (all-NaN actions) and V-JEPA2 (embedding drift), which turned out to be a weight-loading bug and a preprocessing difference, neither ROCm-specific, with fixes going up as their own PRs. Also Cosmos3 nano t2i (22.2 dB against a 23.5 dB floor) and LTX-2.5 audio self-consistency, still open.
Tables from this harness on MI300X and MI325X follow.
Open before review
/work1/...paths, our job marker files). They have to become options.Since the first cut
--tree base=PATHserves a second mstar tree for themstar-basearms, run back to back with the head's on each row, so a change is measured in one session. Without the flag those arms are skipped and nothing else changes.E=..,N=..,K=.., N as w1's rows), after the loader unification in MoE: tuned Triton configs per GPU, the align op on ROCm, AITER fused MoE as an opt-in backend #711.mstar_rustimports from. An arm whose tree carries its own build fails at start if that build isn't the one loaded, and the table says whethermstar_rustcame from the tree or the venv.benchmark/amd/phase_cells.py: worker phases of one mstar row at a workload's concurrencies, sharing long_prompt's server wrapper.Since r8
Since the r8 cut: main's nine new ASR, Command A+ and GLM-5.2 configs are marked unsupported in the correctness map until they have references here, and the harness's own node marker has a neutral name (older result files keep the previous one and are still filtered).
Checks on this rebase
The stack now sits on main f7cb5ca (2026-10-29), every branch cut from one integration tree.
test/ci, the TP lockstep sim,test/rust, CPU Coretest/rust436 passed, CPU Core fails nothing main doesn't (main's own 34:test_dump_stacksx2,loop_output_ownershipx32)test/rocmon one MI325X (a VM slice, torch 2.12.1+rocm7.2)test_*moe*failures are main's GLM-5.2 kernel tests, the same set on the previous headNothing fails on this tree that the previous head doesn't: the failing-set diff against it is empty for
test/rocm, MoE, the sampler and the rows.