commit | 982f172262693198f649d4d8918e5defb1ff6c9c | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 25 10:56:37 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Mar 26 16:25:54 2021 +0000 |
tree | 9a398689cf4350ae6e88d39c7cbc9d23f5896eb7 | |
parent | 236bb730eb4957f9b506e61b2ab086b4b5b663ac [diff] |
Cleaned test case dependencies Also removed hello-world test case. Change-Id: I1a307e480d979ba8fdd3d9dc54b2d473fdd24d99 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