mirror of
https://github.com/deepseek-ai/DeepInfer.git
synced 2026-10-31 16:56:21 +08:00
`h20_ops_ab.py` assumed the TileLang backend is importable, so on a vendor image it could not start at all -- which is exactly where the Triton backend needs checking. Two modes fix that: * `--dump DIR` saves the selected backend's output per case. * `--compare DIR` checks against dumps written elsewhere. Together they answer "do triton 3.5.1 and 3.7.1 agree" without either host having TileLang. Case builders that genuinely need a package the host lacks now report a skip instead of aborting the run, so partial coverage is visible rather than fatal; the import of the sampler's C++-backed inputs moved into the one builder that uses it for the same reason. This is what showed the 19 ported kernels produce element-wise identical output across triton 3.5.1, 3.6.0 and 3.7.1 -- 115 cases, no differences. |
||
|---|---|---|
| .. | ||
| ab_cases.py | ||
| build_vendor.sh | ||
| build.sh | ||
| compare_layers.py | ||
| format_csrc.sh | ||
| gen_stub.sh | ||
| h20_ask.py | ||
| h20_attn_check.py | ||
| h20_engram_check.py | ||
| h20_expert_weight_check.py | ||
| h20_index_decode_check.py | ||
| h20_kv_roundtrip.py | ||
| h20_ops_ab.py | ||
| h20_philox_check.py | ||
| h20_quant_check.py | ||
| h20_real_requant_check.py | ||
| h20_recipe_probe.py | ||
| h20_rng_dump.py | ||
| h20_smoke_check.py | ||
| h20_state_check.py | ||
| h20_topk_check.py | ||
| ref_layer_dump.py | ||
| ref_next_token.py | ||