-
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 failing on Bazel CI #226
Comments
Ah, I see we have This flag is removed recently at bazelbuild/bazel@2b3ad18, so please remove them from config file. |
You can now upgrade protobuf to 3.6.1.2 |
Yes, we had the same problem where protobuf was updated and we had to test on the latest Bazel where the incompatible change with REPOSITORY_NAME was enabled. That is why I added the flag workaround. Will look into this. |
@meteorcloudy Not quite -- 3.6.1.2 is just a tag, but we depend on the individual language releases. The latest release is still 3.6.1 https://github.com/protocolbuffers/protobuf/releases |
-- 224340571 by jingwen <jingwen@google.com>: Update protobuf version in @android_test_support to be compliant with Bazel breaking changes. Bazel HEAD removed the --incompatible_package_name_is_a_function flag, causing upstream protobuf older than 3.6.1 to completely fail to build. This CL updates @android_test_support's protobuf version to 3.6.1.2, which builds with Bazel HEAD. See android/testing-samples#226 PiperOrigin-RevId: 224340571
… Bazel breaking changes. Bazel HEAD removed the --incompatible_package_name_is_a_function flag, causing upstream protobuf older than 3.6.1 to completely fail to build. This CL updates @android_test_support's protobuf version to 3.6.1.2, which builds with Bazel HEAD. See android/testing-samples#226 Also see #147 PiperOrigin-RevId: 224340571
… Bazel breaking changes. Bazel HEAD removed the --incompatible_package_name_is_a_function flag, causing upstream protobuf older than 3.6.1 to completely fail to build. This CL updates @android_test_support's protobuf version to 3.6.1.2, which builds with Bazel HEAD. See android/testing-samples#226 Also see #147 PiperOrigin-RevId: 224340571
… Bazel breaking changes. Bazel HEAD removed the --incompatible_package_name_is_a_function flag, causing upstream protobuf older than 3.6.1 to completely fail to build. This CL updates @android_test_support's protobuf version to 3.6.1.2, which builds with Bazel HEAD. See android/testing-samples#226 Also see #147 PiperOrigin-RevId: 224356109
We can close this now 😄 |
… Bazel breaking changes. Bazel HEAD removed the --incompatible_package_name_is_a_function flag, causing upstream protobuf older than 3.6.1 to completely fail to build. This CL updates @android_test_support's protobuf version to 3.6.1.2, which builds with Bazel HEAD. See android/testing-samples#226 Also see android/android-test#147 PiperOrigin-RevId: 224356109
https://buildkite.com/bazel/bazel-at-release-plus-incompatible-flags/builds/13#6dd83578-ede3-4bf4-bd29-fc6d6a6f66e8
Android Testing is failing with
Bazel@Release + incompatible flags
due toHowever, it is passing with
Bazel@HEAD
, where--incompatible_package_name_is_a_function
is already flipped to true.I don't understand why this is happening, is
android_test_support
embedded in Bazel binary and depends on protobuf? @jinThe text was updated successfully, but these errors were encountered: