Repository navigation
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/24047
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 9 PendingAs of commit 491e1ca with merge base 8d9eec3 ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
|
This PR needs a
|
unittest-cuda has timed out at 90 min on every main run since a04a9f9 made the SDPA autotune tests ~6.5 min slower; the job was already at 83-89 min before that. Split it into a matrix: - kernel: Triton kernel and autotune tests (SDPA, tq4 SDPA, int4 matmul, int5 large GEMM, fused MoE, deltanet, topk, autotune inputs/launch params, mutation cache). ~42 min of pytest. - system: everything else under backends/cuda/tests and passes/tests (lowering passes, op dispatch, export/partitioner/runtime), plus the pybindings device tests, C++ shim tests, and Qwen 3.5 MoE / Gemma 4 31B model tests. ~28 min of pytest. The system shard runs the test directories with the kernel and quantized GEMM files ignored, so new tests default to it. Test plan: CI on this PR; both unittest-cuda shards should finish well under the 90 min timeout.
91352c3 to
491e1ca
Compare
unittest-cudahas hit its 90 min timeout on everymainrun since a04a9f9 (#24004). That commit made the SDPA autotune tests about 6.5 min slower (test_triton_sdpa.pywent from 10.4 to 16.9 min). The job already took 83–89 min before it, so the extra time pushed it over the limit. Example run: https://github.com/pytorch/executorch/actions/runs/39464763398/job/118773442760This PR splits the job into a two-shard matrix:
unittest-cuda (kernel): Triton kernel and autotune tests. That covers SDPA, split-K SDPA, SDPA NaN, tq4 SDPA, int4 matmul, int5 large GEMM, quantized GEMM family, fused MoE, fused deltanet decode, chunk gated delta rule, topk, autotune inputs and launch params, and the Triton mutation cache. About 42 min of pytest.unittest-cuda (system): everything else underbackends/cuda/testsandbackends/cuda/passes/tests. That covers the lowering passes (off-graph KV, DFlash off-graph KV, SDPA split-K replacement), quantized op dispatch, and export, partitioner and runtime tests. This shard also runs the pybindings device tests, the C++ shim tests, and the Qwen 3.5 MoE and Gemma 4 31B model tests. About 28 min of pytest.Kernel tests are listed explicitly in
KERNEL_TESTS. The system shard runs the test directories and passes--ignorefor the kernel files and for the quantized GEMM files thatunittest-cuda-quantized-gemmalready runs, so any new test file goes to the system shard by default. Both shards still do the full install and build, includingexecutor_runner, because both have e2e tests that need it. Both pytest calls now pass--durations=20.Test plan:
backends/cuda/tests/test_*.pyfiles with no overlap.bash -non the script for each shard.python -m unittest .ci/scripts/tests/test_muse_glimmer_batching_ci.pypasses. That test parsescuda.yml.unittest-cudashards should finish well under 90 min.