PEL: Don't allow duplicate callouts
When adding callouts, check if the callout being added already exists.
If it does, don't add it and rather just update the priority of the
existing one to be the highest of the two.
Callouts are considered to be equal if their location code matches, or
if they have the same maintenance procedure, or if they have the same
symbolic FRU.
The change entails adding an operator== on the Callout object, as well
as an operator> so that the callout with the highest priority can be
determined. Also use this new operator> in the sort of the callout list
that happens after a callout is added or changed.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I5ee148cc12e92f67fb3da233c3615e9665e95355
diff --git a/test/openpower-pels/pel_test.cpp b/test/openpower-pels/pel_test.cpp
index a996358..cf54e9c 100644
--- a/test/openpower-pels/pel_test.cpp
+++ b/test/openpower-pels/pel_test.cpp
@@ -958,7 +958,8 @@
ffdcFile.version = 1;
// Write these callouts to a JSON file and pass it into
- // the PEL as an FFDC file.
+ // the PEL as an FFDC file. Also has a duplicate that
+ // will be removed.
auto inputJSON = R"([
{
"Priority": "H",
@@ -967,6 +968,10 @@
{
"Priority": "M",
"Procedure": "PROCEDURE"
+ },
+ {
+ "Priority": "L",
+ "Procedure": "PROCEDURE"
}
])"_json;