clightning-replication: switch system before waiting for server sshd
This is primarily a cosmetic change. - Increases code clarity because all system test blocks now start with `switch_to_system` - Optimizes dependency ordering because `switch_to_system` has no dependency on the server sshd
This commit is contained in:
parent
d332177d3e
commit
0de16095e1
@ -128,8 +128,8 @@ makeTestVM {
|
|||||||
# A gocryptfs has been created
|
# A gocryptfs has been created
|
||||||
client.succeed("ls /var/backup/clightning/lightningd-db/gocryptfs.conf")
|
client.succeed("ls /var/backup/clightning/lightningd-db/gocryptfs.conf")
|
||||||
|
|
||||||
server.wait_for_unit("sshd.service")
|
|
||||||
switch_to_system("replicationRemote")
|
switch_to_system("replicationRemote")
|
||||||
|
server.wait_for_unit("sshd.service")
|
||||||
with subtest("remote replication"):
|
with subtest("remote replication"):
|
||||||
replica_db = "/var/cache/clightning-replication/sshfs/lightningd.sqlite3"
|
replica_db = "/var/cache/clightning-replication/sshfs/lightningd.sqlite3"
|
||||||
client.succeed(f"runuser -u clightning -- ls {replica_db}")
|
client.succeed(f"runuser -u clightning -- ls {replica_db}")
|
||||||
|
Loading…
Reference in New Issue
Block a user