Fix BMC max dump use case to check for capping
Change-Id: Id132990c0857af5bc6d1037bcf39584020d714d9
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/redfish/extended/test_bmc_dump.robot b/redfish/extended/test_bmc_dump.robot
index 3c2fc27..dcd2d4b 100644
--- a/redfish/extended/test_bmc_dump.robot
+++ b/redfish/extended/test_bmc_dump.robot
@@ -155,10 +155,7 @@
# Systems typically hold 8-14 dumps before running out of dump space.
# Attempt to create too_many_dumps. Expect to run out of space
# before this.
- ${too_many_dumps} Set Variable ${100}
-
- # Should be able to create at least this many dumps.
- ${minimum_number_of_dumps} Set Variable ${7}
+ ${too_many_dumps} Set Variable ${20}
# Loop, creating a dump each iteration. Will either get dump_id or
# will get EMPTY when out of dump space.
@@ -170,9 +167,6 @@
Run Keyword If '${dump_id}' != '${EMPTY}' Fail
... msg=Did not run out of dump space as expected.
- Run Keyword If ${n} < ${minimum_number_of_dumps} Fail
- ... msg=Insufficient space for at least ${minimum_number_of_dumps} dumps.
-
Post Dump BMC Performance Test
[Documentation] Check performance of memory, CPU & file system of BMC.