Google Git
Sign in
fuchsia/sdk-samples/drivers/742c918d2973875e84de89329db18ba5508be631
commit
742c918d2973875e84de89329db18ba5508be631
[log]
author
Abseil Team <absl-team@fuchsia.infra.roller.google.com>
Fri Nov 07 22:41:42 2025 -0800
committer
CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Nov 07 22:41:42 2025 -0800
tree
baa34934900b606a218631b54f069f7f499dd7c2
parent
bd56b9f581de7ecd55d6f007531249f13d6e137e [diff]
[roll] Roll third_party/googletest gtest_fail_if_no_test_selected: Rephrase error message.

Sharded tests interact awkwardly with --gtest_fail_if_no_test_selected, but we
can't speak clearly enough to the use cases to complicate the mental model, so
instead we attempt to clarify the simplest approach to debugging a single test
when sharding and --gtest_fail_if_no_test_selected are both in use: unset the
flag.

PiperOrigin-RevId: 829686145
Original-Revision: 37678c92fb183b148163dd173430b4ab88586a26

Roller-URL: https://cr-buildbucket.appspot.com/build/8698790800498844161
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic968ce0bfc4dd634815f8e1584e62037c5c702d6
Reviewed-on: https://fuchsia-review.googlesource.com/c/sdk-samples/drivers/+/1416537
Commit-Queue: GI Roller <global-integration-roller@fuchsia-infra.iam.gserviceaccount.com>
1 file changed
tree: baa34934900b606a218631b54f069f7f499dd7c2
  1. manifests/
  2. scripts/
  3. src/
  4. third_party/
  5. tools/
  6. platform_mappings ⇨ third_party/fuchsia-infra-bazel-rules/config/fuchsia_platform_mappings
  7. .bazelrc
  8. .clang-format
  9. .gitignore
  10. .gitmodules
  11. AUTHORS
  12. BUILD.bazel
  13. CONTRIBUTING.md
  14. driver-samples.code-workspace
  15. fuchsia_env.toml
  16. LICENSE
  17. OWNERS
  18. PATENTS
  19. README.md
  20. rollers.textproto
  21. shac.star
  22. shac.textproto
  23. WORKSPACE.bazel
README.md

Fuchsia samples using the Fuchsia SDK

This repository contains instructions and source code to build, package and run Fuchsia samples using only the Fuchsia SDK.

Set up and bootstrap the SDK driver samples repository

Clone this SDK driver samples repository on your host machine. This repository contains sample driver components and the Bazel-based Fuchsia SDK.

The tasks include:

  • Bootstrap the SDK driver samples repository.
  • Download the SDK toolchain to initialize the SDK environment.
  • Verify that you can run ffx commands.

Do the following:

  1. Open a terminal.

  2. In the terminal, change to your home directory:

    cd

  3. Clone the SDK driver samples repository:

    git clone https://fuchsia.googlesource.com/sdk-samples/drivers fuchsia-drivers --recurse-submodules

    This git clone command creates a new directory named fuchsia-drivers and clones the content of the SDK driver samples repository{:.external}.

  4. Go to the new directory:

    cd fuchsia-drivers

  5. Run the bootstrap script to install Bazel and other required dependencies:

    scripts/bootstrap.sh

  6. Download the SDK toolchain:

    tools/bazel build @fuchsia_sdk//:fuchsia_toolchain_sdk

    The first build may take a few minutes to download dependencies, such as Clang and Fuchsia IDK (which includes the ffx tool).

    When finished successfully, it prints output similar to the following:

    $ tools/bazel build @fuchsia_sdk//:fuchsia_toolchain_sdk
...
INFO: Elapsed time: 23.608s, Critical Path: 0.03s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action

  7. To verify that you can use the ffx tool in your environment, run the following command:

    tools/ffx sdk version

    This command prints output similar to the following:

    $ tools/ffx sdk version
14.20230811.2.1

    At this point, you only need to confirm that you can run ffx commands without error.

    Note: The output above shows the version 14.20230811.2.1, which indicates that this SDK was built and published on August 11, 2023.