featurebase/etcd
Seebs 19dc881d94 test for correct state during test startup
When we've started a fake cluster, we should expect to reach a
"STARTING" state, not a "DOWN" state. This test would coincidentally
pass as long as we checked the state before any of the nodes got
their notification from the node watcher that at least one node was
STARTING, because prior to that the cluster would be DOWN. But once
it got to STARTING, we would wait forever; we never reached the
instruction to tell the nodes to come to any other state, and they
would never reach a DOWN state.
2022-10-06 11:45:50 -05:00
..
config_gen.go set directory permissions restrictively to quiet etcd 2022-09-23 16:56:27 -05:00
embed.go staticcheck is right, as usual 2022-09-14 11:47:50 -05:00
embed_test.go simplify, streamline, and possibly debug embedded etcd 2022-07-21 11:42:35 -05:00
enterprise_cluster.go Fb1463 no cluster build (#2100) 2022-06-09 12:32:46 -07:00
external.go staticcheck is right, as usual 2022-09-14 11:47:50 -05:00
external_test.go [FB-1598] Phase 0 of etcd extraction (#2169) 2022-07-29 15:27:04 -05:00
fake_test.go use timeout when waiting for cluster state changes 2022-09-14 11:47:50 -05:00
leasedkv.go [FB-1598] Phase 0 of etcd extraction (#2169) 2022-07-29 15:27:04 -05:00
leasedkv_test.go test for correct state during test startup 2022-10-06 11:45:50 -05:00
plg_cluster.go Fb1463 no cluster build (#2100) 2022-06-09 12:32:46 -07:00