commit | b3eba2992926f9fc55a836d2baab85adfdf9bc5d | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Feb 10 16:17:08 2021 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Wed Feb 10 16:17:08 2021 -0600 |
tree | 4c4cef45437bea78a8ebabbc8d54dea3f4f75aa5 | |
parent | 9d4f91cd8ab2b8622ab8ff5b6df8d4cbc16e14d6 [diff] |
Attn: Added INFO level trace to test case code Recently defined this for non-test case (dbus logging) code need local unit test case version (std::cout). Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Iff3b6491062fa7e3edf670b3f2cbba7104ea9522
In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.
Aditional details TBD.
For a standard OpenBMC release build, you want something like:
meson -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson -Dtests=enabled <build_dir> ninja -C <build_dir> test