| commit | 3c8aa74d87f885c6a3bbf71c00d93699b5e91ab1 | [log] [tgz] |
|---|---|---|
| author | Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@intel.com> | Wed May 21 15:19:35 2025 +0200 |
| committer | Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@intel.com> | Wed May 21 15:19:35 2025 +0200 |
| tree | 8c5f11a9e051ff4d8ea1256ba16b82168ed8ebc7 | |
| parent | 583ba441654657bb4ba9d051b747144a7258c159 [diff] |
fix random UT fails Tests TestNumericThresholdWithDwellTime/SleepAfterEveryUpdate/2, 6 and 9 could fail randomly because next update happened at the same time when timer from one of previous updates was supposed to expire - if update got processed first, timer was canceled and test failed Tested: Before this change UTs failed almost 100% of the time on my machine, with this change 0 failures in 500 iterations Change-Id: I11940027fca377b7be67cb82b638bf162616d37e Signed-off-by: Boleslaw Ogonczyk Makowski <boleslawx.ogonczyk-makowski@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].