commit | bb742807632c37d2c188cc864ba8e72d070e08d7 | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Thu Mar 10 08:12:22 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 24 17:50:13 2022 +0000 |
tree | 89ae2c894218e46d7ad187c6301ad833ecb44e35 | |
parent | ebddb4216dc9a435c106b883a116bca8d432dffb [diff] |
Add unit test for Attention class Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: Ia1f451b7e990ecdf29903944e12c5a9ea5585eeb
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