Commit graph

24 commits

Author SHA1 Message Date
92dd2bbe15 jepsen: nlnet task3a seems to fix things 2023-11-16 18:09:13 +01:00
18e5811159
jepsen: add patch and use more complete names 2023-11-16 12:57:21 +01:00
5b1f50be65 jepsen: testing 2023-10-25 14:43:24 +02:00
db921cc05f jepsen: reconfigure nemesis + add db nemesis 2023-10-25 11:41:34 +02:00
d13bde5e26 jepsen: set1 and set2 don't fail anymore ?? 2023-10-24 15:44:05 +02:00
d2c365767b jepsen: more testing 2023-10-24 11:39:45 +02:00
9030c1eef8 jepsen: code path for nemesis final generator 2023-10-20 15:53:46 +02:00
654775308e jepsen: add cluster reconfiguration nemesis 2023-10-20 15:48:37 +02:00
f5b0972781 jepsen: register crdt read-after-write is fixed with deleteobject patch 2023-10-20 15:00:10 +02:00
d148b83d4f jepsen: reg2 failure seems to happen only with deleteobject 2023-10-20 13:36:48 +02:00
4b93ce179a jepsen: errors in reg2 workload under investigation 2023-10-20 12:56:55 +02:00
74e50edddd jepsen: refactoring 2023-10-19 14:34:19 +02:00
b3bf16ee27 make jepsen test more robust: handle errors and timeouts, fixed access key 2023-10-18 17:51:34 +02:00
ddd3de7fce refactor jepsen code 2023-10-18 16:30:45 +02:00
ef5ca86dfc jepsen: update to garage 0.9.0 2023-10-18 14:01:18 +02:00
0bb1577ae1 two set workloads with different checkers 2023-10-18 12:03:11 +02:00
6eb26be548 Add garage set test (this one works :p) 2023-10-18 12:03:11 +02:00
eb86eaa6d2 refactor jepsen test 2023-10-18 12:03:11 +02:00
93a7132b4c the fix for increasing timestamps does not make things linearizable 2023-10-18 12:03:11 +02:00
dc5245ce65 even without nemesis, s3 get/put/delete is not linearizable (is this normal?) 2023-10-18 12:03:11 +02:00
70c1d3db46 better match exceptions 2023-10-18 12:03:11 +02:00
bc11701999 jepsen: s3 gets and puts 2023-10-18 12:03:11 +02:00
ca4cc7e44f jepsen connects to vagrant vms 2023-10-18 12:03:11 +02:00
7011b71fbd jepsen: wip 2023-10-18 12:03:11 +02:00