Repository navigation
[rocm] Raise the unittest-rocm-gfx950 timeout to 150 minutes - #23646
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23646
Note: Links to docs will display an error until the docs builds have been completed. ⏳ 2 Pending, 1 Unrelated FailureAs of commit 0928594 with merge base 9875560 ( BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Since #23603 the QuantizedGemmFamily kernels compile and run on gfx950 instead of failing fast at the Triton compile, and unittest-rocm-gfx950 went from ~28 to ~80 minutes (job 113766563170: 10:02-11:22, pytest 67.6 min). About 37 of those minutes are Int4AutotunePickTest's CPU-saturated AOTI compile, which is the point of that test. At a 90-minute timeout one run was already cancelled. Raise the job's timeout to 150 minutes rather than drop or split suites. The other gfx950 jobs in this workflow use 180.
501df8a to
0928594
Compare
This PR needs a
|
Since #23603 the QuantizedGemmFamily kernels compile and run on gfx950 instead of failing fast at the Triton compile. As a result
unittest-rocm-gfx950went from ~28 to ~80 minutes (https://github.com/pytorch/executorch/actions/runs/37914177023/job/113766563170: 10:02–11:22, pytest 67.6 min). At the current 90-minute timeout one run was already cancelled (https://github.com/pytorch/executorch/actions/runs/37848283613/job/113554882943).Where the time goes (gfx950, with #23642):
test_int4_quantized_gemm.pyInt4AutotunePickTest36.6)test_int8_quantized_gemm.pytest_int5_quantized_gemm.pyInt4AutotunePickTest's time is the CPU-saturated AOTI compile, which is what that test exercises.Change
timeoutfrom 90 to 150 minutes. The other gfx950 jobs in this workflow use 180.Test plan
CI:
unittest-rocm-gfx950completes instead of being cancelled at 90 minutes.