GitHub Runner Timeout Troubleshooting

ocsGitHub

GitHub Runner Timeout

 Troubleshooting

If you need to run a job for longer than six hours, there are a couple of options.

Self-Hosted Runners: You can use self-hosted runners, which allow you to bypass the six hour limit. Self-hosted runners will give you more control over the environment and can run jobs for longer periods

Timeout Configuration: You can specify a larger timeout value in your workflow configuration using the timeout-minutes parameter. However,Use this mightarticle not work forwhen GitHub hostedActions runners due to the enforced time limit

How to create self hosted runner in GitHub

Set Up Your Self-Hosted Runner

Access your repository on GitHub.

Navigate to Settings > Actions > Runners.

Click Add runner and follow the instructions to download and configure the runner application on your machine1.

Register the Runner

Run the provided registration command on your machine to connect it to your GitHub repository.

This will involve running a script that registers your machine asor a self-hosted runner1.

GitHub runner times

Configureout Yourwhile Workflow:

starting,

controlling, or

Invalidating yourAIQ workflowwork. YAML file, specifyCorrected the runs-title prefix and focused the content on keytimeout to use your self-hosted runner. diagnosis.

Here

Common ischecks

an

• Confirm example yaml file with runs-on self-hosted andwhether the timeout settings.occurs
  in

  jobs:
  GitHub build:
  Actions, runs-on:the self-hosted
  runner timeout-minutes:host, 720AIQ #startup, Exampletest 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

1. Capture the workflow run ID, runner name, timestamps, and failing step.
2. Compare GitHub logs with AIQ logs for 12the hours
   same steps:
   time -window.
3. Increase name:timeout Checkoutvalues code
   only uses:after actions/checkout@v2
   confirming #the Addjob youris stepsmaking here

progress.Document whether the root cause was capacity, network, credentials, test duration, or artifact handling.