| commit | 5e47b162d100b66507d8b065e8a31c7b3221c2f2 | [log] [tgz] |
|---|---|---|
| author | Jayanth Othayoth <ojayanth@gmail.com> | Sun Jun 08 01:13:29 2025 -0500 |
| committer | Jayanth Othayoth <ojayanth@gmail.com> | Sun Jun 08 01:33:44 2025 -0500 |
| tree | b7e577b44bdbfc30feb216062832372d7636ed74 | |
| parent | e77b83201175011e663db2b91e53853d01179cee [diff] |
clang-tidy: mark unused ioc field in test stub
The 'ioc' field in DbusSensorObject test stub is intentionally
unused but retained to align with the base implementation.
Marked it with [[maybe_unused]] to suppress clang-tidy's
-Wunused-private-field warning while preserving interface
consistency for future compatibility.
Error details:
'''
tests/src/stubs/dbus_sensor_object.cpp:17:5: error:
class ‘stubs::DbusSensorObject’ does not have any field named ‘ioc’
17 | ioc(ioc), bus(bus), objServer(objServer)
'''
Change-Id: Id86a671b255f98ea22fddca82c24ad2192727235
Signed-off-by: Jayanth Othayoth <ojayanth@gmail.com>
This component implements middleware for sensors and metrics aggregation.
This application is implementation of Telemetry proposed in OpenBMC design docs [1].
It's responsible for:
[2],[3] updates.[4]There are two way to build telemetry service:
To build it using bitbake follow the guide from OpenBMC docs[5]. To build it using meson follow the quick guide to install meson[6] and then run below commands
meson build
cd build
ninja
After successful build you should be able to run telemetry binary or start unit tests
./tests/telemetry-ut ./telemetry
In case if system is missing boost dependency, it is possible to build it locally and set BOOST_ROOT environment variable to location of built files for meson. After this change meson should be able to detect boost dependency. See [7] for more details.
More information can be found in OpenBMC docs repository [8].