commit | 69e3771f9e131c97a3ca7f139170988bd3e8fb48 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 24 16:43:03 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 29 13:19:15 2022 -0500 |
tree | 76d1921d89bb9ce04629c4da6349a33c57e06e80 | |
parent | 985388a8a5960e234182a0f3cb9cbaf7a8f3b91e [diff] |
Consolidate test cases for readability Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ifb927b680d15980cd52dea743d0acb1391dac443
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