commit | 96d5486c3ca5c5037e6f74bd3a1d196d91b80829 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Sep 17 11:16:12 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Sep 20 22:24:07 2021 -0500 |
tree | e10d31c66344f8cce3d4bece88dc4953d25090bd | |
parent | 84721d9083afd9781834d69be33c3fb9a4559309 [diff] |
More test cases for Resolution class Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ic887f97c4aae8d194657f9925cbd8336d3e0feef
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