Update logging-test file check on BMC
Changes:
- Modify BMC execute command keyword and also the
method using test binary utility command to check
logging-test file existence on BMC.
Tested:
Ran successfully
robot -v OPENBMC_HOST:xx.xx.xx.xx
-v DEBUG_TARBALL_PATH:./debug-tarball.tar.xz
redfish/systems/eventlog/test_event_logging.robot
Change-Id: If555ce6f9bbd040a75b21278bc8b506acaf45846
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/lib/logging_utils.robot b/lib/logging_utils.robot
index 74209ab..16222a6 100644
--- a/lib/logging_utils.robot
+++ b/lib/logging_utils.robot
@@ -132,12 +132,10 @@
Logging Test Binary Exist
[Documentation] Verify existence of prerequisite logging-test.
- Open Connection And Log In
- ${out} ${stderr}= Execute Command
- ... which /tmp/tarball/bin/logging-test return_stderr=True
+ ${stdout} ${stderr} ${rc}=
+ ... BMC Execute Command test -f /tmp/tarball/bin/logging-test print_out=1
Should Be Empty ${stderr} msg=Logging Test stderr is non-empty.
- Should Contain ${out} logging-test
- ... msg=Logging test returned unexpected result.
+
Clear Existing Error Logs
[Documentation] If error log isn't empty, reboot the BMC to clear the log.