1 files changed, 11 insertions, 11 deletions
diff --git a/src/test/isolation/specs/read-write-unique-4.spec b/src/test/isolation/specs/read-write-unique-4.spec
index ec44782348..9002248811 100644
--- a/src/test/isolation/specs/read-write-unique-4.spec
+++ b/src/test/isolation/specs/read-write-unique-4.spec
@@ -17,27 +17,27 @@ teardown
   DROP TABLE invoice;
 }
 
-session "s1"
+session s1
 setup { BEGIN ISOLATION LEVEL SERIALIZABLE; }
-step "r1" { SELECT COALESCE(MAX(invoice_number) + 1, 1) FROM invoice WHERE year = 2016; }
-step "w1" { INSERT INTO invoice VALUES (2016, 3); }
-step "c1" { COMMIT; }
+step r1 { SELECT COALESCE(MAX(invoice_number) + 1, 1) FROM invoice WHERE year = 2016; }
+step w1 { INSERT INTO invoice VALUES (2016, 3); }
+step c1 { COMMIT; }
 
-session "s2"
+session s2
 setup { BEGIN ISOLATION LEVEL SERIALIZABLE; }
-step "r2" { SELECT COALESCE(MAX(invoice_number) + 1, 1) FROM invoice WHERE year = 2016; }
-step "w2" { INSERT INTO invoice VALUES (2016, 3); }
-step "c2" { COMMIT; }
+step r2 { SELECT COALESCE(MAX(invoice_number) + 1, 1) FROM invoice WHERE year = 2016; }
+step w2 { INSERT INTO invoice VALUES (2016, 3); }
+step c2 { COMMIT; }
 
 # if they both read first then there should be an SSI conflict
-permutation "r1" "r2" "w1" "w2" "c1" "c2"
+permutation r1 r2 w1 w2 c1 c2
 
 # cases where one session doesn't explicitly read before writing:
 
 # if s2 doesn't explicitly read, then trying to insert the value
 # generates a unique constraint violation after s1 commits, as if s2
 # ran after s1
-permutation "r1" "w1" "w2" "c1" "c2"
+permutation r1 w1 w2 c1 c2
 
 # if s1 doesn't explicitly read, but s2 does, then s1 inserts and
 # commits first, should s2 experience an SSI failure instead of a
@@ -45,4 +45,4 @@ permutation "r1" "w1" "w2" "c1" "c2"
 # (s1, s2) or (s2, s1) where s1 succeeds, and s2 doesn't see the row
 # in an explicit select but then fails to insert due to unique
 # constraint violation
-permutation "r2" "w1" "w2" "c1" "c2"
+permutation r2 w1 w2 c1 c2