commit | ab1e4dda8239b54920ff1a38bde4b1f58b0d322b | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Mon Mar 14 22:34:47 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 24 17:50:30 2022 +0000 |
tree | b73321ca358811495945d1cc1600218669436d94 | |
parent | bb742807632c37d2c188cc864ba8e72d070e08d7 [diff] |
Add unit test for util's data-file.hpp/cpp files Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: I23a2786bc8ec8d5adc7be2b35e4db7fb950edadf
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