.gitea/workflows/android.yml uses runs-on: ubuntu-latest, a label no runner in the fleet advertises (labels are ubuntu-amd64, ubuntu-arm, ubuntu-amd64-4090, gpu-amd64, macos-latest). Result: the workflow has never been scheduled — GET /actions/tasks returns 0 runs for the repo.
Pegging alone won't turn it green: the ubuntu-amd64 label runs jobs in catthehacker/ubuntu:act-latest, which has no ANDROID_HOME/SDK, so the workflow's echo "sdk.dir=$ANDROID_HOME" > local.properties writes an empty path and the Android Gradle plugin fails.
Fix: runs-on: ubuntu-amd64 + android-actions/setup-android@v3 (platform 35 / build-tools 35.0.0 per compileSdk) + write local.properties after the SDK exists + cache: gradle on setup-java. Delete the inert .github/workflows/android.yml duplicate.
`.gitea/workflows/android.yml` uses `runs-on: ubuntu-latest`, a label no runner in the fleet advertises (labels are `ubuntu-amd64`, `ubuntu-arm`, `ubuntu-amd64-4090`, `gpu-amd64`, `macos-latest`). Result: the workflow has never been scheduled — `GET /actions/tasks` returns 0 runs for the repo.
Pegging alone won't turn it green: the `ubuntu-amd64` label runs jobs in `catthehacker/ubuntu:act-latest`, which has no `ANDROID_HOME`/SDK, so the workflow's `echo "sdk.dir=$ANDROID_HOME" > local.properties` writes an empty path and the Android Gradle plugin fails.
Fix: `runs-on: ubuntu-amd64` + `android-actions/setup-android@v3` (platform 35 / build-tools 35.0.0 per compileSdk) + write `local.properties` after the SDK exists + `cache: gradle` on setup-java. Delete the inert `.github/workflows/android.yml` duplicate.
Resolved in spikersoft-android PR #1 (merged). Pegged to ubuntu-amd64 + in-job Android SDK provisioning — first Android CI run ever went green on 4090-4. Closing.
Resolved in spikersoft-android PR #1 (merged). Pegged to `ubuntu-amd64` + in-job Android SDK provisioning — first Android CI run ever went green on 4090-4. Closing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
.gitea/workflows/android.ymlusesruns-on: ubuntu-latest, a label no runner in the fleet advertises (labels areubuntu-amd64,ubuntu-arm,ubuntu-amd64-4090,gpu-amd64,macos-latest). Result: the workflow has never been scheduled —GET /actions/tasksreturns 0 runs for the repo.Pegging alone won't turn it green: the
ubuntu-amd64label runs jobs incatthehacker/ubuntu:act-latest, which has noANDROID_HOME/SDK, so the workflow'secho "sdk.dir=$ANDROID_HOME" > local.propertieswrites an empty path and the Android Gradle plugin fails.Fix:
runs-on: ubuntu-amd64+android-actions/setup-android@v3(platform 35 / build-tools 35.0.0 per compileSdk) + writelocal.propertiesafter the SDK exists +cache: gradleon setup-java. Delete the inert.github/workflows/android.ymlduplicate.Resolved in spikersoft-android PR #1 (merged). Pegged to
ubuntu-amd64+ in-job Android SDK provisioning — first Android CI run ever went green on 4090-4. Closing.