| commit | 79cbe2445a2d0df15a72e7bdfbcb315efc81b968 | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit@fuchsia.infra.roller.google.com> | Wed Jan 10 19:46:49 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 10 11:48:26 2024 -0800 |
| tree | bb2a1cba58ac5561eb15301d64e8bdf3d687270d | |
| parent | fef85358a703666f11c523d4dc424d36f1ed60a0 [diff] |
[roll] Roll fuchsia [bazel_sdk] Enable remote builds for Bazel SDK test suite This change allows the Bazel SDK test suite to use RBE when `enable_bazel_remote_rbe = true` is set in `args.gn`. Note that currently, 17 tests are failing when executed remotely, because Python 3 is not installed on the builder's container image (intentionally). This works as follows: - Modify the fuchsia_platform_build_repository() rule to generate a BUILD.bazel file that contains a platform() definition named `host` that contains the appropriate `exec_properties` to enable remote builds for any action that needs to run on the host. - Modify .bazelrc to use --host_platforms=host to enable this, and --host_crosstool_top to avoid unnecessary Bazel errors (see .bazelrc comment for details). This replicates what is done through //build/bazel/templates/template.platform_mappings in the Fuchsia platform build, only differently. Previous changes to //build/bazel/bazel_sdk/BUILD.gn ensure that `bazel_test.py` will be invoked with `--bazelrc=...../remote_services.bazelrc --bazel-config=remote` to enable remote builds for the test run. Original-Bug: b/317291511 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/971374 Original-Revision: 90ae2547c56db46beb7285281d0d0b35e8a8c2a0 GitOrigin-RevId: 4cd4bb6d7e03bbb42aaf53ccfefefb29386fa186 Change-Id: I6f1200583f16bbc75182b8ecc19733362d725875
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.