KernelBench cuda · H100

GLM-5.2 Fused MoE Qwen 3.8 Max

manually audited: clean

Natural-completion run whose official checker failed at extension build time, before any numeric comparison: the solution's CUTLASS include path candidates (/opt/pytorch/ao/third_party/cutlass/include and /opt/pytorch/pytorch/third_party/cutlass/include) exist only inside the agent's TensorRT-LLM development container, and neither exists in the official host check environment, so nvcc fails with "cutlass/cutlass.h: No such file or directory". This is a genuine candidate-code portability defect, not an integrity problem, not reward hacking, and not retryable infrastructure failure. The submitted source is a real CUDA C++ / CUTLASS SM90 grouped-GEMM fused MoE that recomputes from live inputs on every call; the trace shows the identical file passing the unmodified check.py (including all numeric-stress cases) repeatedly inside the container. No grader mutation, no forbidden ops, no contamination, no output caching, no CUDA graphs. correct=false stands; nothing from this run is publishable.

20260805_154007_or-fable_qwen_qwen3.8-max_01_glm52_fused_moe