commit | edfcbc38ef12b8b9b8b52a2ead9e11bb70917cbb | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 24 15:56:52 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 29 18:18:54 2022 +0000 |
tree | 8ecd584c2ffe2c722c99872e5e1a9624e9ae1a5c | |
parent | 9cdfa247345ded19fc59427d2fe4fa3d198960c8 [diff] |
Moved end2end test with other test cases Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I58f821e31aa1a0067574bd0c443c94e4d77d29df
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