Fix eSEL parsing from logging entry "AdditionalData"
Resolves openbmc/openbmc-test-automation#1000
Change-Id: Id5d93459b80d413b2624cc2e2e3fcec77d6061bc
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/lib/openbmc_ffdc_methods.robot b/lib/openbmc_ffdc_methods.robot
index 45e1ca7..a451f3d 100755
--- a/lib/openbmc_ffdc_methods.robot
+++ b/lib/openbmc_ffdc_methods.robot
@@ -354,9 +354,9 @@
# Example: /xyz/openbmc_project/logging/entry/1/callout
\ Continue For Loop If '${entry_path.rsplit('/', 1)[1]}' == 'callout'
\ ${esel_data}= Read Attribute ${entry_path} AdditionalData quiet=${1}
- \ ${length}= Get Length ${esel_data}
- # Skip writting to file if eSEL AdditionalData is empty
- \ Continue For Loop If ${length} == ${0}
+ \ ${status}= Run Keyword And Return Status
+ ... Should Contain Match ${esel_data} ESEL*
+ \ Continue For Loop If ${status} == ${False}
\ ${index}= Get Esel Index ${esel_data}
\ Write Data To File "${esel_data[${index}]}" ${logpath}
\ Write Data To File ${\n} ${logpath}