Repository navigation
Give test-qnn-python-imports-linux 30 minutes instead of 15 - #24092
Merged
Merged
Conversation
The job's `timeout` becomes the job-level timeout-minutes, so it covers pulling the QNN image, checking out submodules and the cache setup steps, not just the script. Over the last day the successful runs took 9 to 15 minutes (often over 13), and 5 of the last 14 runs on main went past 15 and were killed. GitHub reports a timed-out job as "cancelled", which counts as a failure for the pull workflow. Raise the limit to 30 minutes, the smallest value already used in this workflow, so an ordinary slow runner no longer fails the job. Test plan: none locally; this only changes a CI limit. Timings come from the job and step durations of recent runs in the Actions API.
shoumikhin
added
the
release notes: none
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/24092
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit c8e0968 with merge base 6368414 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
Bot
added
the
CLA Signed
Gasoonjia
approved these changes
Oct 23, 2026
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
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.
Problem
test-qnn-python-imports-linuxhas a 15 minute timeout, the shortest inpull.yml. That limit becomes the job'stimeout-minutes, so it also covers pulling the large QNN image, checking out submodules and the cache setup steps, not only the test script.Those setup steps vary from run to run. Over the last day, successful runs took 9 to 15 minutes, often over 13. Runs that went past 15 were killed. 5 of the last 14 runs on main ended this way, with the script itself taking its usual 7 to 8 minutes. When the job hits the limit, GitHub cancels it, and the
pullrun on that commit ends as cancelled instead of green.Fix
Raise the limit to 30 minutes, the smallest value already used in this workflow. A slow runner then no longer fails the job, and a real hang is still caught.
Testing
No local test, since this only changes a CI limit. The timings above come from the job and step durations of recent runs.