Slow bridge test

[gerardsn]

Nodes A, B, C, D, E are split in two groups: A, B, C and C, D, E, where C has a long gossip interval.

If the nodes don't sync fast enough, C causes the network to form a split brain.

Not sure if the test should be added to the e2e flow (run every time) since it can take several minutes to complete.

[woutslakhorst]

This is one out of many scenarios. The outcome of this test does not identify problems in the code due to changes (PRs) but more architectural and protocol problems. It should be part of a test suite where we evaluate the protocol and make adjustments according to. It should therefore be part of a larger test scenario.

[gerardsn]

This is one out of many scenarios. The outcome of this test does not identify problems in the code due to changes (PRs) but more architectural and protocol problems. It should be part of a test suite where we evaluate the protocol and make adjustments according to. It should therefore be part of a larger test scenario.

That sounds like a better place for this test. What should I do with this test for now?

[woutslakhorst]

maybe we clone this repo, remove all tests but that one. Then we have a network test suite that can be run manually?