| commit | b3e03d2d6b42298411d29329b5456d62da289461 | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Fri Jun 28 13:55:47 2024 +0200 |
| committer | Michal Orzel <michalx.orzel@intel.com> | Fri Jun 28 15:13:43 2024 +0200 |
| tree | 8b97917406ebe9325149afd43dad84e6e860512c | |
| parent | 4444a13c9af8d581797bd43f378be51a614d60f5 [diff] |
Address Valgrind issues in CI Fixes "uninitialized values" errors reported by Valgrind. Problem occurred from lack of specializations of googletest's PrintTo functions for several custom types. Tested: On local CI container. After applying this patch issues stopped appearing. Change-Id: I98d9fd19724bee15add7b19422a9ddc2e4cbef09 Signed-off-by: Michal Orzel <michalx.orzel@intel.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].