pldm: use run_until to remove timeout-as-success ambiguity in host tests base_host, inventory_host, unexpected_eid_host, and unexpected_eid_fw_host all queue one command, run the FD, and check the response, then relied on run_terminus timing out to signal "done" -- indistinguishable from a real hang. Add a shared run_fd_step helper (common.rs) that uses run_until to bound each of these to exactly one step, so every error they can now hit is real. firmware_update_host's own multi-step flow (an unbounded number of RequestFirmwareData/TransferComplete/VerifyComplete/ApplyComplete round trips per call) doesn't fit a fixed step count and keeps using run_terminus directly; it already gained a direct run_until test in the prior commit. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The OpenPRoT Technical Charter can be found at https://github.com/OpenPRoT/.github/blob/main/GOVERNANCE.md
NOTE: We are converting our build system to bazel. We recommend installing bazelisk to automatically manage bazel versions.
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.The project is structured as a bazel module.
No additional tools are required - all dependencies are managed by bazel.