-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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 testing CI faliing (all platforms) #307
Comments
It looks like the latest green is still using 28.0.2, whereas this project's HEAD is already using 29.0.2, which no longer exists on Bazel CI. Perhaps we can also install 28.0.2 build tools on Bazel CI? @philwo |
@jin I'll install all 28.x and 29.x build tools releases on our CI machines today, but will this actually fix the issue? I thought we're incompatible with <29.x since bazelbuild/bazel#10079? |
This is a chicken and egg problem :) the build-tools were updated to 29.0.2, which the Android rules now need (for a specific build scenario), but the latest green commit is still using 28.0.2, which the CI doesn't have, so it's failing with missing input errors. We need 28.0.2 on the CI to at least get past the missing input errors, or maybe manually update the latest green commit to f08dda5? |
LGTM, I'll roll out new images with 28.x and 29.x build tools on all platforms tomorrow morning and will retry the failed jobs then. 👍 |
thanks @philwo! |
@jin These versions are installed now:
However, a rebuild still fails: https://buildkite.com/bazel/android-testing/builds/641 Do we have to revert f08dda5 because this project isn't compatible with build-tools 29.0.2? |
Android Testing CI has been failing for many days, and thus it's been difficult to diagnose issues with it failing with Bazel@HEAD
Here is a failure for Unbuntu 16 this morning using Bazel@HEAD:
I think this dependency was updated in a recent commit?
https://buildkite.com/bazel/android-testing
The text was updated successfully, but these errors were encountered: