commit | 9cdfa247345ded19fc59427d2fe4fa3d198960c8 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 24 13:24:46 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 29 18:18:54 2022 +0000 |
tree | 908fe45d82b4877ec11dd03c87ce1221583c49f9 | |
parent | 30984d1574cb4154c625f0925afcd76e65b984e8 [diff] |
Limit test_arg to test code Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I642d99db826262c31cc79d64d0e5a3e4ea46c2c8
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