android / android/testing-samples
Flag --incompatible_disallow_empty_glob will break Android Testing in Bazel 1.2.1
- Dominant language
- Java
- Stars
- 9.3k
- Forks
- 3.6k
- PR merge metrics
- No merged PRs in 30d
Description
Incompatible flag --incompatible_disallow_empty_glob will break Android Testing once Bazel 1.2.1 is released.
Please see the following CI builds for more information:
* [:windows: (OpenJDK 8)](:windows: (OpenJDK 8))
* [:ubuntu: 18.04 (OpenJDK 11)](:ubuntu: 18.04 (OpenJDK 11))
* [:darwin: (OpenJDK 8)](:darwin: (OpenJDK 8))
* [:ubuntu: 16.04 (OpenJDK 8)](:ubuntu: 16.04 (OpenJDK 8))
Questions? Please file an issue in https://github.com/bazelbuild/continuous-integration
**Important**: Please do NOT modify the issue title since that might break our tools.
Contributor guide
Research direction
Open the four linked Bazelisk incompatible-flags CI builds and inspect the reported Android testing failures. The issue directs follow-up questions to the bazelbuild/continuous-integration repository; trace the failing sample or test there and confirm what must change for Bazel 1.2.1 compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100