commit | 11f08e82f7982a64088271cb0196569fa38c8c04 | [log] [tgz] |
---|---|---|
author | Saša Živkov <sasa.zivkov@sap.com> | Thu Jan 18 15:13:31 2024 +0100 |
committer | Saša Živkov <sasa.zivkov@sap.com> | Thu Jan 18 15:13:31 2024 +0100 |
tree | 61854625f71771072bba3055fc92e973e83a88ed | |
parent | b987059fc495f838a252bf276ae39fcbf0895c02 [diff] |
LockTest fix misleading variable name The insertLockRow is used for various tests to insert locks. Not all inserted locks will be stale. Change-Id: I8d16e8f1d0367668df76a1a121391dfcdd1a49b4
diff --git a/src/test/java/com/googlesource/gerrit/plugins/spannerrefdb/LockTest.java b/src/test/java/com/googlesource/gerrit/plugins/spannerrefdb/LockTest.java index fb1eec5..f9f691c 100644 --- a/src/test/java/com/googlesource/gerrit/plugins/spannerrefdb/LockTest.java +++ b/src/test/java/com/googlesource/gerrit/plugins/spannerrefdb/LockTest.java
@@ -171,7 +171,7 @@ } private void insertLockRow(Timestamp timestamp) { - Mutation staleLock = + Mutation insertLock = Mutation.newInsertBuilder("locks") .set("project") .to(PROJECT_NAME_KEY.get()) @@ -184,6 +184,6 @@ .set("owner") .to("") .build(); - dbClient.write(Collections.singletonList(staleLock)); + dbClient.write(Collections.singletonList(insertLock)); } }