-
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
Fix Bazel incompatible changes #239
Comments
This is blocked on android-test (https://github.com/android/android-test) pushing out the patch to fix the IC. Internal context: cl/226047055 |
android-test is unblocked, but I discovered more issues. Also two blockers that require a new Protobuf release: bazelbuild/bazel#5825 (comment) |
…mpatible changes around Starlark APIs Work towards android/testing-samples#239 PiperOrigin-RevId: 229790580
…mpatible changes around Starlark APIs Work towards android/testing-samples#239 PiperOrigin-RevId: 229790580
…mpatible changes around Starlark APIs Work towards android/testing-samples#239 PiperOrigin-RevId: 229790580
…mpatible changes around Starlark APIs Work towards android/testing-samples#239 PiperOrigin-RevId: 229790580
…mpatible changes around Starlark APIs Work towards android/testing-samples#239 PiperOrigin-RevId: 229838054
I still see failures with:
|
Looks like there's a new Protobuf release 3.7.0, let me test it out.. |
android-testing itself is fine -- the incompatible changes come from android/android-test and its deps. Tried to bump android-test's protobuf version to 3.7.0-rc2, but failed: protocolbuffers/protobuf#5696 We also need to bump its usage of rules_kotlin to a commit later than https://github.com/bazelbuild/rules_kotlin/tree/cab5eaffc2012dfe46260c03d6419c0d2fa10be0 |
Is it possible to fix at least |
Thanks for the ping! This dropped off my radar. #246 |
@jin Can you try to update to Protobuf 3.7.1? |
So this is turning out to be more complicated than expected. Protobuf 3.7.1 introduces a dependency on a bind |
The |
Blocked on protocolbuffers/protobuf#6048 Once that's in, we need to bump the version and sha256 of javalite.zip in android/android-test#304, and merge that in. Once that's done, we can then update this repository to use the new android-test release. |
If it helps, rules_closure was updated: https://github.com/bazelbuild/rules_closure/pull/344/files |
That's the main protobuf version. android-test (and transitively this project) has a dependency on protobuf's javalite rules which is released separately from 3.7.1, and the javalite branch hasn't been updated with the incompatible changes. |
Any update? |
…mpatible changes around Starlark APIs Work towards android/testing-samples#239 PiperOrigin-RevId: 229838054
This repository isn't compatible with Bazel with the flag
--all_incompatible_changes
.e.g. it fails with
--incompatible_no_transitive_loads
(https://buildkite.com/bazel/bazel-at-release-plus-incompatible-flags/builds/56#48b4d6c0-6ef6-4a1a-858c-7a68229fc715):Fixing the issues will ensure the code remains compatible with the future changes in Bazel. Let me know if you need any help.
cc @jin
The text was updated successfully, but these errors were encountered: