commit | a79f6c8fa6bc8fec117f64d14ae7f62fc8b0d48b | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Jan 12 16:38:49 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Jan 12 16:38:49 2021 -0600 |
tree | 4332c9f3f53b5d19b528860c5ff855904b4ce909 | |
parent | 9fb657f9bac9adf2bad14ebfc564b2660f5cd275 [diff] |
Clean up warnings from Jenkins CI Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I6d9dd7909a4ec6c07c820fc3fa208226927c04c9
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