Common Issues

OverviewCopy Anchor Link

Refer to this page if your runners aren't picking up jobs, after you onboarded.

Bot permissionsCopy Anchor Link

Check if the WarpBuild bot has access to the repo. Navigate to WarpBuild GitHub settings > Click on 'Configure on GitHub' for the organization. And check the list of repositories.

Runner group checksCopy Anchor Link

Default runner groupCopy Anchor Link

1. If you are using a public repo, please validate that you have enabled WarpBuild on your public repos.

Non-default runner groupCopy Anchor Link

If you are using a non-default runner group, which can be validated by going to WarpBuild > Runners > Default GitHub runner group.

1. Check if this runner group has access to the repo. Navigate to GitHub (or your GitHub Enterprise host) > Organization Settings > Actions > Runner Groups > Click on the runner group which is selected on WarpBuild.

2. Check if there are workflow restrictions. GitHub supports restricting workflows based on workflow path, sha, branch and tags. For example, monalisa/octocat/.github/workflows/cd.yaml@refs/heads/main only picks jobs of cd.yaml on main.

Android instrumentation tests are slow or don't workCopy Anchor Link

If an Android CI job using reactivecircus/android-emulator-runner is taking much longer than usual, the emulator has likely fallen back to software emulation because it couldn't access /dev/kvm. Add this step before the emulator step:

- name: Enable KVM group perms
  run: |
    echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' \
      | sudo tee /etc/udev/rules.d/99-kvm4all.rules
    sudo udevadm control --reload-rules
    sudo udevadm trigger --name-match=kvm

This is required in all GitHub compatible runners. Learn more.

Jobs on custom VM images die with a shutdown signalCopy Anchor Link

A job on a BYOC custom Linux image fails a few minutes in with The runner has received a shutdown signal. The image has unattended-upgrades enabled, and its post-upgrade service restart stops warpbuild-agentd. Disable it in the image. Learn more.

Running DependabotCopy Anchor Link

Open your custom runner from Runners > Custom, click Edit, and check 'Allow Dependabot' under 'GitHub jobs'.

This setup will run all your Dependabot workflows on WarpBuild custom runners.