Fixed feature tests

pg-sharding · Mar 28, 2024 · 641fdb5 · 641fdb5
1 parent e663843
commit 641fdb5
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/qdb/memqdb.go b/qdb/memqdb.go
@@ -271,7 +271,7 @@ func (q *MemQDB) TryLockKeyRange(lock *sync.RWMutex, id string, read bool) error
 		res = lock.TryLock()
 	}
 	if !res {
-		return spqrerror.Newf(spqrerror.SPQR_KEYRANGE_ERROR, "key range \"%s\" is already locked", id)
+		return spqrerror.Newf(spqrerror.SPQR_KEYRANGE_ERROR, "key range \"%s\" is locked", id)
 	}
 
 	if _, ok := q.Krs[id]; !ok {

diff --git a/test/feature/features/coordinator.feature b/test/feature/features/coordinator.feature
@@ -235,7 +235,7 @@ Feature: Coordinator test
     """
     Then SQL error on host "router" should match regexp
     """
-    context deadline exceeded
+    key range "krid1" is locked
     """
 
     Given I run SQL on host "coordinator"
@@ -342,7 +342,7 @@ Feature: Coordinator test
     """
     Then SQL error on host "coordinator" should match regexp
     """
-    context deadline exceeded
+    key range "krid1" is locked
     """
 
     When I run SQL on host "coordinator"

diff --git a/test/feature/features/proxy_console.feature b/test/feature/features/proxy_console.feature
@@ -98,7 +98,7 @@ Feature: Proxy console
         """
         Then SQL error on host "router2" should match regexp
         """
-        context deadline exceeded
+        key range "krid1" is locked
         """
 
         When I run SQL on host "router-admin"