Android emulators: add bp-kvm
The Android emulator needs hardware acceleration (KVM). Add the bp-kvm label next to your BuildPulse runner label and the job runs on a machine with /dev/kvm ready to use.
Add bp-kvm to runs-on
Keep your runner label and add bp-kvm after it. That is the whole change:
jobs:
android-tests:
runs-on: [bp-ubuntu-latest-x64-4x, bp-kvm]
steps:
- uses: actions/checkout@v4
- uses: actions/setup-java@v4
with: { distribution: temurin, java-version: '17' }
- uses: reactivecircus/android-emulator-runner@v2
with:
api-level: 34
arch: x86_64
script: ./gradlew connectedCheckThe job gets /dev/kvm, already readable and writable by the runner user, and an x86_64 emulator boots headless with -accel on. The usual "Enable KVM group perms" step from GitHub's examples works as written, and you can leave it out.
Sizes and price
bp-kvm works with every x64 runner size, from bp-ubuntu-latest-x64-2x up, and with the x64 Docker builder sizes. It is billed as the size you picked, at that size's price per minute. Only the jobs that carry bp-kvm use it, so the rest of your workflows are unchanged.
arm64 runners do not support it: the emulator needs x64 hardware virtualization. A job that asks for bp-kvm on an arm64 label is not started; move that job to an x64 label.
If the emulator says it needs acceleration
x86_64 emulation currently requires hardware acceleration means the job ran without bp-kvm. Add the label and re-run the job.
Run your Android tests on BuildPulse
Pick an x64 size, add bp-kvm, and point one workflow at it.
3,000 free minutes every month · No credit card required