bazelbuild / bazelbuild/rules_android
android_local_test tests are very fragile
- Dominant language
- Java
- Stars
- 203
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
At head, with Bazel 7.0.0rc1, these tests fail because the resolved JDK paths aren't what is expected:
```
USE_BAZEL_VERSION=7.0.0rc1 bazel test --enable_bzlmod=false --incompatible_enable_android_toolchain_resolution=false --java_runtime_version=17 -- //test/rules/android_local_test:android_local_test_default_launcher
FAIL: //test/rules/android_local_test:android_local_test_default_launcher (see /usr/local/google/home/jcater/.cache/bazel/_bazel_jcater/ddb4e20e0e2e6bca92f5deeef02ce168/execroot/rules_android/bazel-out/k8-fastbuild/testlogs/test/rules/android_local_test/android_local_test_default_launcher/test.log)
INFO: From Testing //test/rules/android_local_test:android_local_test_default_launcher:
==================== Test output for //test/rules/android_local_test:android_local_test_default_launcher:
In test _android_local_test_default_launcher from //test/rules/android_local_test:java_launcher_test.bzl: Expect runfiles to contains ../remotejdk17_linux/bin/java but was ...
```
(Full log attached)
[alt.log](https://github.com/bazelbuild/rules_android/files/13057284/alt.log)
Contributor guide
Assessment
This issue has not been assessed yet.