Repository navigation
ci: stop setup-android from requesting the removed tools package - #85
Merged
Merged
Conversation
Both Android arm64 jobs now fail in "Set up Android SDK", before any goffi
code runs:
Warning: Failed to find package 'tools'
Error: The process '/usr/local/lib/android/sdk/cmdline-tools/16.0/bin/sdkmanager' failed with exit code 1
android-actions/setup-android@v3 defaults its `packages` input to
`tools platform-tools` and runs `sdkmanager <pkg>` for each entry. Google's
SDK repository index (repository2-3.xml) no longer contains a `tools`
package, while `platform-tools` and `cmdline-tools` are still listed, so
the `tools` call exits 1. The same breakage is tracked upstream in
android-actions/setup-android#537. The last green run of these jobs on main
was for c8f74c6 on 2026-09-10; the workflow has not changed since, and the
failure is identical on a docs-only PR.
Nothing in this workflow or in scripts/check-android-arm64.sh uses the
`tools` package. Pass `packages: platform-tools`, which keeps everything
the step installed before except the package that no longer exists. The
action still accepts licenses, exports ANDROID_HOME and puts sdkmanager on
PATH, which the following NDK step relies on.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
kolkov
approved these changes
Oct 15, 2026
kolkov
left a comment
kolkov
left a comment
Contributor
There was a problem hiding this comment.
Thanks — straightforward and well explained.
Checked: android-actions/setup-android@v3 takes the packages input, nothing in ci.yml or scripts/check-android-arm64.sh uses the obsolete tools package, and both Android arm64 jobs are green on this branch.
Since #83, #84, #87, #88 and #89 all carry this commit, we'll merge this one first so the others shrink to their own changes after a rebase.
LGTM.
kolkov
added
area: ci
kolkov
added a commit
that referenced
this pull request
Oct 15, 2026
Android arm64 is a preview platform (docs/ANDROID.md: physical-device startup validation is still pending), but android-cross was in CI Success's needs, so an Android-only failure blocked every pull request, including ones that do not touch Android code. The October 2026 setup-android breakage (fixed in #85) showed the cost. Remove android-cross from CI Success's needs and its summary. The jobs still run on every PR and their result stays visible. continue-on-error is deliberately not used: it would paint a broken Android build green. Document the policy and the condition for re-gating in ci.yml and docs/ANDROID.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both Android arm64 jobs now fail in "Set up Android SDK", before any goffi code runs:
android-actions/setup-android@v3 defaults its
packagesinput totools platform-toolsand runssdkmanager <pkg>for each entry. Google's SDK repository index (repository2-3.xml) no longer contains atoolspackage, whileplatform-toolsandcmdline-toolsare still listed, so thetoolscall exits 1. The same breakage is tracked upstream in android-actions/setup-android#537. The last green run of these jobs on main was for c8f74c6 on 2026-09-10; the workflow has not changed since, and the failure is identical on a docs-only PR.Nothing in this workflow or in scripts/check-android-arm64.sh uses the
toolspackage. Passpackages: platform-tools, which keeps everything the step installed before except the package that no longer exists. The action still accepts licenses, exports ANDROID_HOME and puts sdkmanager on PATH, which the following NDK step relies on.