PEL: Change python plugin error traces to debug
There's been lots of complaints and questions about what these are, if
they're important, and why they show up so much so just make them debug
traces. The plugin parser developers can still enable debug traces to
see the errors if they notice some unparsed sections.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If68e0e080eff92225331e39c3c41faa007fe785e
diff --git a/extensions/openpower-pels/src.cpp b/extensions/openpower-pels/src.cpp
index f4807f5..9da5992 100644
--- a/extensions/openpower-pels/src.cpp
+++ b/extensions/openpower-pels/src.cpp
@@ -254,10 +254,10 @@
}
if (!pErrStr.empty())
{
- log<level::ERR>("Python exception thrown by parser",
- entry("ERROR=%s", pErrStr.c_str()),
- entry("SRC=%s", hexwords.front().c_str()),
- entry("PARSER_MODULE=%s", module.c_str()));
+ log<level::DEBUG>("Python exception thrown by parser",
+ entry("ERROR=%s", pErrStr.c_str()),
+ entry("SRC=%s", hexwords.front().c_str()),
+ entry("PARSER_MODULE=%s", module.c_str()));
}
return std::nullopt;
}