| commit | 120c8e64af88047d285d695e22fb9d83e97538f1 | [log] [tgz] |
|---|---|---|
| author | Austin Foxley <afoxley@pigweed.infra.roller.google.com> | Thu May 15 23:48:48 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 15 23:48:48 2025 -0700 |
| tree | fa80364c1038d4550a9d6f7589c8e34dfcaad363 | |
| parent | 34c643dd2f616df2ba37bbd9113fdf04e1119d85 [diff] |
roll: pigweed pw_unit_test: If SetUp fails skip test body https://google.github.io/googletest/faq.html#CtorVsSetUp says this: In the body of a constructor (or destructor), it’s not possible to use the ASSERT_xx macros. Therefore, if the set-up operation could cause a fatal test failure that should prevent the test from running, it’s necessary to use abort and abort the whole test executable, or to use SetUp() instead of a constructor. This implies that we should check for *_ASSERT failure after SetUp runs and stop running further tests. Due to how this is currently implemented, we will also skip further tests if an *_EXPECT fails since we don't differentiate between the two failure types in the framework state. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/292043 Tests-Not-Needed: Austin Foxley <afoxley@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Original-Revision: e0318cbf853bd2838ef0be854ae747593c445093 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: a1e03da2c0a45d..e0318cbf853bd2 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8714735108875306081 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie58a902a5c1626afb0b4da15e1a36e5e322e9187 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/292232 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It is a LED-blinking service (featuring RPC control!) for the Raspberry Pi Pico. It can also be run on any computer using the included simulator.
git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart cd pw_bazel_quickstart
The only dependency that must be installed is Bazelisk.
Bazelisk is a launcher for the Bazel build system that allows for easy management of multiple Bazel versions.
Instructions for installing Bazelisk can be found here.
To run the simulator, type: bazelisk run //apps/blinky:simulator_blinky Then, in a new console, connect to the simulator using: bazelisk run //apps/blinky:simulator_console
To start, connect a Raspberry Pi Pico, Pico 2, or debug probe via USB.
To run on the Raspberry Pi Pico, type: bazelisk run //apps/blinky:flash_rp2040 Then, in a new console, connect to the device using: bazelisk run //apps/blinky:rp2040_console
Once connected with a console, RPCs can be sent to control the LED. Try running:
device.set_led(True) device.set_led(False) device.toggle_led() device.blink(blink_count=3)
bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.
bazelisk run @pigweed//targets/rp2040/py:unit_test_server in one console followed by bazelisk test //... --config=rp2040 will also allow running the unit tests on-device.
Try poking around the codebase for inspiration about how Pigweed projects can be organized. Most of the relevant code in this quickstart (including RPC definitions) is inside modules/blinky, with some client-side Python code in tools/console.py.