Ignas Anikevicius
Ignas Anikevicius
@mattem, should this PR be continued?
Feel free to reopen PR later. Closing to clean things up.
My experiment to have a GH action push back gazelle manifest changes back failed, it seems that we would require extra permissions from the workflow. @dependabot recreate
@rickeylev I can consistently reproduce build failure when running: ``` USE_BAZEL_VERSION=last_green RULES_PYTHON_ENABLE_PYSTAR=1 bazelisk test //python/tests/toolchains:python_3_9_10_x86_64-unknown-linux-gnu_test 2023/10/17 09:12:13 Using unreleased version at commit 14e3d1b825dab76c5886fffb9dd1c01841c18795 2023/10/17 09:12:13 Downloading https://storage.googleapis.com/bazel-builds/artifacts/centos7/14e3d1b825dab76c5886fffb9dd1c01841c18795/bazel... Extracting Bazel installation......
Doing a `bisect`: ```console $ RULES_PYTHON_ENABLE_PYSTAR=1 bazelisk --bisect=2c9d68e05861ac3e71cb86de2b69bc52403411bf..HEAD test //python/tests/toolchains:python_3_9_10_x86_64-unknown-linux-gnu_test ``` yielded the following known to work commits: * https://github.com/bazelbuild/bazel/commit/75657569220178f11ec12f7ce33812e571c6c854 (passes) * https://github.com/bazelbuild/bazel/commit/2b8219042c (passes) Then there is a series of...
Create bazelbuild/bazel#1496 for the current CI issues.
Let's close this as complete as it is working well. Thank you @rickeylev!
@UebelAndre , could you please paste the error you get without this PR? Maybe we are only fixing the symptom if we add the linux arm constant to the platforms,...
It looks like the `platform` is not used for anything but checking if `windows` is in the platform string, which suspects me that we could potentially remove the keyed attribute....