-
Notifications
You must be signed in to change notification settings - Fork 84
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
bazel: update to 3.1.0 #850
Conversation
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Taking a look at what it would mean to update to 3.1.0 to avoid the linking issue with bazelisk. I understand this is sweeping the underlying problem under the rug by complying with what is installed in the CI machines, but I'd rather unblock CI and then figure out how to correctly install and link bazelisk in macos. Created envoyproxy/envoy#11210 to track in upstream |
Signed-off-by: Alan Chiu <achiu@lyft.com>
.github/workflows/android.yml
Outdated
@@ -89,7 +89,7 @@ jobs: | |||
- run: ls -lh dist/ | |||
- name: start simulator | |||
run: ./ci/mac_start_emulator.sh | |||
- run: bazel mobile-install --fat_apk_cpu=x86 --start_app //examples/kotlin/hello_world:hello_envoy_kt | |||
- run: bazel mobile-install --host_force_python=PY2 --fat_apk_cpu=x86 //examples/kotlin/hello_world:hello_envoy_kt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- run: bazel mobile-install --host_force_python=PY2 --fat_apk_cpu=x86 //examples/kotlin/hello_world:hello_envoy_kt | |
- run: bazel mobile-install --host_force_python=PY2 --fat_apk_cpu=x86 //examples/kotlin/hello_world:hello_envoy_kt |
from error message: bazelbuild/bazel#7899
Note: The failure of target @bazel_tools//tools/android:incremental_install (with exit code 1) may have been caused by the fact that it is a Python 2 program that was built in the host configuration, which uses Python 3. You can change the host configuration (for the entire build) to instead use Python 2 by setting --host_force_python=PY2.
If this error started occurring in Bazel 0.27 and later, it may be because the Python toolchain now enforces that targets analyzed as PY2 and PY3 run under a Python 2 and Python 3 interpreter, respectively. See https://github.com/bazelbuild/bazel/issues/7899 for more information.```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, that is just a red herring they already updated to pyhon 3 in bazelbuild/bazel@d93a146#diff-947a45ac6fb178dbfb7cc530fddd6b9a
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
…-3.1.0 Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: Jose Nino <jnino@lyft.com>
closing in favor of #854 |
Signed-off-by: Jose Nino jnino@lyft.com