Browse Source
To reproduce the next bug, I had to ensure that one node keeps thinking it's disconnected, then the other node reconnects, then the first node realizes it's disconnected. This code does that, adding a '0' dev-disconnect modifier. That means we fork off a process which (due to pipebuf) will accept a little data, but when the dev_disconnect file is truncated (a hacky, but effective, signalling mechanism) will exit, as if the socket finally realized it's not connected any more. The python tests hang waiting for the daemon to terminate if you leave the blackhole around; to give a clue as to what's happening in this case I moved the log dump to before killing the daemon. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>ppa-0.6.1
Rusty Russell
7 years ago
committed by
Christian Decker
7 changed files with 67 additions and 9 deletions
Loading…
Reference in new issue