Repository navigation
[cuda] Move the large-M quantized GEMM suites out of unittest-cuda too - #23676
Merged
Merged
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23676
Note: Links to docs will display an error until the docs builds have been completed. This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
Bot
added
the
CLA Signed
This PR needs a
|
unittest-cuda is cancelled at its 90-minute timeout on every recent main commit. #23605 moved the quantized GEMM kernel suites into unittest-cuda-quantized-gemm, but the same push added test_int4_large_quantized_gemm.py (~7.7 min on the A10G) and test_int6_large_quantized_gemm.py (~5.1 min), which still run in unittest-cuda. On #23635 its backends/cuda/tests pytest alone took 62 min and the job was cancelled during the Gemma 4 tests that follow. Run both in the second quantized-GEMM shard, renamed large-int5-int6-int8-graph-timing (that shard took 44 min; the int4 shard already takes ~60). unittest-cuda ignores them. No test is dropped.
Gasoonjia
force-pushed
the
gasoonjia/move-large-quantized-gemm-suites
branch
from
October 12, 2026 02:03
a1b602f to
b3337e1
Compare
rascani
approved these changes
Oct 12, 2026
This branch was successfully 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
2 participants
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.
unittest-cudais cancelled at its 90-minute timeout on every recent main commit (e.g. https://github.com/pytorch/executorch/actions/runs/37991426749/job/114026586806). #23605 moved the quantized GEMM kernel suites intounittest-cuda-quantized-gemm, but the same push also added two new suites that still run inunittest-cuda:test_int4_large_quantized_gemm.py(711dd81e23, ~7.7 min on the A10G)test_int6_large_quantized_gemm.py(f19360763f, ~5.1 min)On #23635 (https://github.com/pytorch/executorch/actions/runs/38006402026/job/114076255669),
unittest-cuda'sbackends/cuda/testspytest alone took 62 min, and the job was cancelled during the Gemma 4 tests that follow.Change
large-int5-int6-int8-graph-timing. That shard took 44 min on [cuda] Score autotune picks with one event tick of tolerance, on longer kernels #23635; the int4 shard already takes ~60 min, so they don't go there.unittest-cudaignores them.Test plan
CI:
unittest-cudafinishes within 90 min.unittest-cuda-quantized-gemm (large-int5-int6-int8-graph-timing)runs both large suites and also stays within 90 min.