commit | 9491cdb459603350d0634c7ed01da39f0269bf76 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 01 10:40:45 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 01 10:57:56 2022 -0600 |
tree | bd1568fa30882414dc923b42a0e03885bc718519 | |
parent | 4334a3667815dcf3e0c6ce64c8b03cdcf3c852ce [diff] |
Modify PLL test case to get plugin from RAS data files Instead of inputing the exact plugin name for test. Force the test case to query the RAS data files for the appropriate plugin name. Change-Id: I589f33869e6894499c5b03f7bb4f67034bfe7a67 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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