Add temperature, power, frequency tests to GPU stress test
Add GPU temperature, power, frequency utilities to
utils_os.robot, and remove the common Test Setup Execution
utility from syslib.
Resolves openbmc/openbmc-test-automation#1030
Resolves openbmc/openbmc-test-automation#637
Change-Id: I823b9956b61d9c35b09faa4e7a4372aa9244a805
Signed-off-by: Steven Sombar <ssombar@us.ibm.com>
diff --git a/systest/htx_hardbootme_test.robot b/systest/htx_hardbootme_test.robot
index f0a0fba..c1b2fd5 100755
--- a/systest/htx_hardbootme_test.robot
+++ b/systest/htx_hardbootme_test.robot
@@ -12,8 +12,9 @@
# HTX_INTERVAL The time delay between consecutive checks of HTX
# status, for example, 15m.
# In summary: Run HTX for $HTX_DURATION, looping
-# $HTX_LOOP times checking for errors every $HTX_INTERVAL.
-# Then allow extra time for OS Boot, HTX startup, shutdown.
+# $HTX_LOOP times checking for errors every
+# $HTX_INTERVAL. Then allow extra time for OS
+# Boot, HTX startup, shutdown.
# HTX_KEEP_RUNNING If set to 1, this indicates that the HTX is to
# continue running after an error was found.
# CHECK_INVENTORY If set to 0 or False, OS inventory checking before
@@ -115,7 +116,7 @@
Rprintn
Rpvars loop_count estimated_loop_time estimated_time_remaining
- Boot To OS
+ REST Power On stack_mode=skip
# Post Power off and on, the OS SSH session needs to be established.
Login To OS
@@ -208,6 +209,19 @@
... AND Sleep ${HTX_INTERVAL}
+Test Setup Execution
+ [Documentation] Do the initial test setup.
+
+ REST Power On stack_mode=skip
+ Delete All Error Logs
+ Tool Exist htxcmdline
+
+ # Shutdown if HTX is running.
+ ${status}= Run Keyword And Return Status Is HTX Running
+ Run Keyword If '${status}' == 'True'
+ ... Shutdown HTX Exerciser
+
+
Test Teardown Execution
[Documentation] Do the post test teardown.
# 1. Shut down HTX exerciser if test Failed.