commit 5d05994be83faca347457a7d93301f5c364105ff
author Sushil Singh <susilsi7@in.ibm.com> Mon Sep 27 08:41:38 2021 -0500
committer George Keishing <gkeishin@in.ibm.com> Tue Oct 19 04:36:57 2021 +0000
tree 3536c73bd2ee124838a6c052e69c54924e017cc5
parent e7e9171e96b36ae0214bb577bf7cf74b3f6a8359

Automation fix for lock management

changes:
    - Using different set of locks type and
      segment value is used when one
      lock is trying to lock on another lock

Change-Id: I90639b92e7b1902a09ced875e1703c650856d65d
Signed-off-by: Sushil Singh <susilsi7@in.ibm.com>

openpower/ext_interfaces/test_lock_management.robot

diff --git a/openpower/ext_interfaces/test_lock_management.robot b/openpower/ext_interfaces/test_lock_management.robot
index 22e0095..92a8c1e 100644
--- a/openpower/ext_interfaces/test_lock_management.robot
+++ b/openpower/ext_interfaces/test_lock_management.robot
@@ -76,9 +76,9 @@
     [Template]  Verify Acquire Lock Fails On Another Lock
 
     # client_id    lock_type
-    HMCID-01       ReadCase2,WriteCase2
-    HMCID-01       WriteCase2,WriteCase2
-    HMCID-01       WriteCase2,ReadCase2
+    HMCID-01       ReadCase7,WriteCase6
+    HMCID-01       WriteCase6,WriteCase6
+    HMCID-01       WriteCase6,ReadCase7
 
 
 Acquire Lock After Reboot