-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
android_local_test
isn't compatible with Android Platforms
#19829
Comments
Is this a blocker for flipping the flag? If one of the android rules would fail with it? |
I've marked it as a blocker for Bazel 7 release (not for starting the release, but for finishing it), but we need someone from the rules_android team to investigate because the code is pretty confusing. |
@bazel-io fork 7.0.0 |
Error log from
The problem (I think) is that the test sets |
Hullo! We're trying to get 7.0 blockers under control and this one seems to not have been investigated yet. Could we get an initial triage and an estimate on how long this'll take to fix? |
@ahumesky was investigating, I'll ask him to update. |
I have a change out for review that should address this |
1. Remove `target_compatible_with` from the Android toolchains generated in the Starlark and native `android_sdk_repository` rules so that they can be selected with a host JDK in android_local_test 1. Re-enable `android_local_test_integration_test.sh` 1. Switch `--platforms` to `--android_platforms` in the android integration test setup so that a host JDK can be selected in android_local_test Fixes bazelbuild#19829 RELNOTES: None PiperOrigin-RevId: 582716155 Change-Id: I49d6a9058218d522b9ebb7cc6842fe20c36e2798
…20215) 1. Remove `target_compatible_with` from the Android toolchains generated in the Starlark and native `android_sdk_repository` rules so that they can be selected with a host JDK in android_local_test 1. Re-enable `android_local_test_integration_test.sh` 1. Switch `--platforms` to `--android_platforms` in the android integration test setup so that a host JDK can be selected in android_local_test Fixes #19829 RELNOTES: None Commit 9bbc2cb PiperOrigin-RevId: 582716155 Change-Id: I49d6a9058218d522b9ebb7cc6842fe20c36e2798 Co-authored-by: Googler <ahumesky@google.com>
…in (Starlark) android_sdk_repository so that it can be selected along with a host JDK in android_local_test. bazelbuild/bazel#19829 PiperOrigin-RevId: 582777002 Change-Id: If480dce6c4d35e40934fe326c1362c8f446ff848
…in (Starlark) android_sdk_repository so that it can be selected along with a host JDK in android_local_test. bazelbuild/bazel#19829 PiperOrigin-RevId: 582777002 Change-Id: If480dce6c4d35e40934fe326c1362c8f446ff848
Forked from #18262.
The
android_local_test
rule is a strange beast which wants to do two things: it wants to build an APK, using a valid Android SDK.But, it also wants to run a Java binary on the local platform, with that APK as a data file. This worked before #18262, but now that we are being honest about Java versions, the cracks show up.
This sounds like a case for execution groups to me, but I also don't actually understand how this works under the hood.
For now, this means that we need to disable testing
android_local_test
with Android Platforms, and get the code cleaned up.We probably also need to fix the Starlark version in bazelbuild/rules_android.
The text was updated successfully, but these errors were encountered: