GitHub Runner Timeout Troubleshooting
GitHub Runner Timeout Troubleshooting
Use this article when GitHub Actions or a self-hosted GitHub runner times out while starting, controlling, or validating AIQ work. Corrected the title prefix and focused the content on timeout diagnosis.
Common checks
- Confirm whether the timeout occurs in GitHub Actions, the runner host, AIQ startup, test execution, or artifact upload.
- Review workflow timeout settings, job-level timeouts, and step-level timeouts.
- Check runner host CPU, memory, disk space, network access, and service availability.
- Validate AIQ Controller/Test Node reachability from the runner.
- Reduce the workflow to a small smoke execution before running the full suite.
Resolution workflow
- Capture the workflow run ID, runner name, timestamps, and failing step.
- Compare GitHub logs with AIQ logs for the same time window.
- Increase timeout values only after confirming the job is making progress.
- Document whether the root cause was capacity, network, credentials, test duration, or artifact handling.
Last updated: October 9, 2026