commit | d700609cb6dbae60e4698ecf62b92b906f369067 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Feb 05 14:55:52 2021 -0600 |
committer | ben.tyner <ben.tyner@ibm.com> | Wed Feb 10 04:36:05 2021 +0000 |
tree | 9b823a4b1e5ba11c9ad18c4385553a27849db77f | |
parent | 8882c32a2cbbfd047a5ff0424af027bd6f3ad0fd [diff] |
Attn: Fix CI complaint of unused-results Use the results provided by file read/write operations. For mismatch in number of bytes written on ffdc data creation we add a trace message, for mismatch in number of bytes read during pel creation we skip creating the pel. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I3ec6755ef258ac869775b08afafae324a76a2884
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