-
Notifications
You must be signed in to change notification settings - Fork 41
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
BazelCI has numerous problems #171
Comments
Closed
#175 is another example of this. |
copybara-service bot
pushed a commit
that referenced
this issue
Oct 30, 2023
This splits the "tools" and "rules" tasks, because each needs different flags to be applied. This also disables failing tests, fixing #171. (See https://buildkite.com/bazel/rules-android/builds/2036) PiperOrigin-RevId: 577853284 Change-Id: I1b62d7b7ef641a1a4431f8f7136a66dc9d9c3c76
With 90bbf87, CI is green, but all the underlying issues still need to be fixed. |
jylinv0
pushed a commit
to jylinv0/rules_android
that referenced
this issue
Jan 23, 2024
Trying to deal with bazelbuild#171. Closes bazelbuild#172. PiperOrigin-RevId: 576123681 Change-Id: I719482de8c385d4bdec069615f6e403788564aad
jylinv0
pushed a commit
to jylinv0/rules_android
that referenced
this issue
Jan 23, 2024
This splits the "tools" and "rules" tasks, because each needs different flags to be applied. This also disables failing tests, fixing bazelbuild#171. (See https://buildkite.com/bazel/rules-android/builds/2036) PiperOrigin-RevId: 577853284 Change-Id: I1b62d7b7ef641a1a4431f8f7136a66dc9d9c3c76
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been digging into the recent failures in rules_android BazelCI.
There are a number of errors present.
--incompatible_enable_android_toolchain_resolution
to fix this for now, and eventually add the flagsAfter we stabilize, we need to add Android Platforms flags.
The text was updated successfully, but these errors were encountered: