commit | 7ec2dd11c37ec04459771bcf418689378da6911b | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Wed Apr 13 09:16:16 2022 -0500 |
committer | austinfcui <austinfcui@gmail.com> | Wed Apr 13 09:16:16 2022 -0500 |
tree | 5de60fdfd14721aa259a7e438a072813d19e8967 | |
parent | 6a69e6e5fc726125ca5fb4b3ae4b13d6e22ba03c [diff] |
Eliminate warning messages from test-attention.cpp file Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: Ib933179c8d11486333bfb60a477a3a47dfc7e685
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