c-parsons
c-parsons
See https://github.com/bazelbuild/bazel/issues/7977#issuecomment-488118667 We would suggest that users set default values for rules via a wrapper macro. Wrapper macros become more annoying to write, though, if they need to mirror the...
The readme for the android app tutorial target reads: "Once these are done, set up the android_sdk_repository rule in the WORKSPACE file, **following the instructions in the comments there.**" There...
Breakage: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2211#845f819e-3ae0-457b-8389-4e381d5e7168 ``` (16:09:28) ERROR: /var/lib/buildkite-agent/builds/bk-docker-53p6/bazel-downstream-projects/rules_k8s/examples/hellogrpc/BUILD:61:16: in jsonnet_to_json rule //examples/hellogrpc:deployment: -- | Traceback (most recent call last): | File "/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/40d71967fca1731c50aad85c7f24c1eb/external/io_bazel_rules_jsonnet/jsonnet/jsonnet.bzl", line 239, column 34, in _jsonnet_to_json_impl | transitive_files = depset(transitive_data), ...
Some workflows apply a top level aspect to a build, such as: ``` bazel build //foo:bar --aspect=//baz:my_aspect.bzl%my_aspect ``` It would be nice to have a canonical test rule which would...
I got some feedback today that it was unclear how to access the `target_under_test` target in analysistest (`ctx.attr.analysis_test` returns a list!) We can alleviate some of this confusion with a...
One may want to specify: ``` analysis_test( name = "my_test", targets = ["foo.o"], ``` But currently `targets` does not support files. At first glance, this would seem easy to implement,...
Failing on RBE with 16.04/ Example buildkite failure: https://buildkite.com/bazel/bazel-toolchains/builds/22557#0a001b16-56d1-47e8-a9fc-6476b826408f Seems to have been failing since Dec 17. ``` Executing tests from //tests/rbe_repo:rbe_autoconf_custom_toolchain_config_suite_spec_export_test ----------------------------------------------------------------------------- File external/rbe_autoconf_custom_toolchain_config_suite_spec_export/test/rbe_autoconf_root/rbe-test-output/config/rbe_autoconf_custom_toolchain_config_suite_spec_export/test_config_dir/bazel_3.7.1/cc/test.BUILD does not exist. ```
There are a number of downstream projects failing with Bazel@HEAD, and culprit finder is no help. Perhaps some infrastructure change? Error occurs while downloading repository dependencies, and is of the...
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1905#e9759395-101f-4047-b7c9-daa0fc4eb714 Broken only on Bazel@HEAD all OSes, verified it's not a one-off flake. Failure has no culprit, looks like it might be machine configuration? Not sure how to diagnose. Error...