tests: avoid placement new in test files The prior commit 842113b5349cd8dcb1bdbcc8d2845449ffe8317f replaced placement new calls with std::start_lifetime_as in production code, but the same pattern remained in a number of test files. GCC-16 -Wuninitialized handling of placement new caused these tests to fail at runtime with SIGSEGV, assertion failures, or timeouts. Convert all remaining placement new calls in the test files to std::start_lifetime_as with the same polyfill for GCC-15 compatibility. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id2a87647a232b4332fbfead8cf3e49c8995993cc
PLDM (Platform Level Data Model) is a key component of the OpenBMC project, providing a standardized data model and message formats for various platform management functionalities. It defines a method to manage, monitor, and control the firmware and hardware of a system.
The OpenBMC PLDM project aims to implement the specifications defined by the Distributed Management Task Force (DMTF), allowing for interoperable management interfaces across different hardware and firmware components.
To build and run PLDM, you need the following dependencies:
MesonNinjaAlternatively, source an OpenBMC ARM/x86 SDK.
To build the PLDM project, follow these steps:
meson setup build && meson compile -C build
The simplest way of running the tests is as described by the meson man page:
meson test -C build
Alternatively, tests can be run in the OpenBMC CI docker container using these steps.
pldm daemon accepts a command line argument --verbose or --v or -v to enable the daemon to run in verbose mode. It can be done via adding this option to the environment file that pldm service consumes.
echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd systemctl restart pldmd
rm /etc/default/pldmd systemctl restart pldmd
For complete documentation on the functionality and usage of this repository, please refer to the docs folder.