commit: 0ea2428d4db0e17571caf67ccd3f4334716eaeaa
[log] [tgz]
author: Chris Frantz <cfrantz@google.com>
Tue Mar 17 13:42:36 2026 -0700
committer: cfrantz <frantzcj+github@gmail.com>
Wed Mar 18 21:00:58 2026 -0700
tree: d4e21105158bc718d4b349210d800a8bc0abdc05
parent: 4d0d5435325c9412f1e705e59c080f7adc088c6d [diff]

earlgrey: Re-arrange tests

Move the existing earlgrey tests into `//target/earlgrey/tests`

Signed-off-by: Chris Frantz <cfrantz@google.com>

target/earlgrey/tests/ipc/user/BUILD.bazel[Renamed from target/earlgrey/ipc/user/BUILD.bazel - diff]
target/earlgrey/tests/ipc/user/system.json5[Renamed from target/earlgrey/ipc/user/system.json5 - diff]
target/earlgrey/tests/ipc/user/target.rs[Renamed from target/earlgrey/ipc/user/target.rs - diff]
target/earlgrey/tests/threads/kernel/BUILD.bazel[Renamed from target/earlgrey/threads/kernel/BUILD.bazel - diff]
target/earlgrey/tests/threads/kernel/system.json5[Renamed from target/earlgrey/threads/kernel/system.json5 - diff]
target/earlgrey/tests/threads/kernel/target.rs[Renamed from target/earlgrey/threads/kernel/target.rs - diff]
target/earlgrey/tests/unittest_runner/BUILD.bazel[Renamed from target/earlgrey/unittest_runner/BUILD.bazel - diff]
target/earlgrey/tests/unittest_runner/system.json5[Renamed from target/earlgrey/unittest_runner/system.json5 - diff]
target/earlgrey/tests/unittest_runner/target.rs[Renamed from target/earlgrey/unittest_runner/target.rs - diff]

9 files changed

tree: d4e21105158bc718d4b349210d800a8bc0abdc05

README.md

OpenPRoT

Technical Charter

The OpenPRoT Technical Charter can be found at https://github.com/OpenPRoT/.github/blob/main/GOVERNANCE.md

Getting Started

NOTE: We are converting our build system to bazel. We recommend installing bazelisk to automatically manage bazel versions.

Available Tasks

You can run tasks using the Pigweed workflow launcher pw or bazel.

./pw presubmit - Run presubmit checks: formatting, license checks, C/C++ header checks and clippy.
./pw format - Run the code formatters.
bazel test //... - Run all tests.
bazel build //docs - Build documentation.

Development

The project is structured as a bazel module.

Requirements

Bazel. We recommend installing bazelisk to automatically manage bazel versions.

No additional tools are required - all dependencies are managed by bazel.