commit | 5191bae9d11562c826c6c1f719815548894def3a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Aug 04 22:48:28 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Aug 05 14:42:26 2021 -0500 |
tree | 56edca87d457c9c3444c67e9fbfd4db9c265f92f | |
parent | e5411f0f4d862fac11a9a32cac058a438ef5ed54 [diff] |
Util functions to validate JSON and find data files Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ifc1537f7c8eabab08690d5a74023377572564895
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