core-lightning/lightningd/test
Rusty Russell 5889ad5fc4 dev-disconnect: add blackhole option.
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>
2017-09-06 19:11:21 +02:00
..
Makefile Makefiles: simplify dependencies. 2017-08-29 17:54:14 +02:00
run-channel.c Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
run-commit_tx.c Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
run-cryptomsg.c dev-disconnect: add blackhole option. 2017-09-06 19:11:21 +02:00
run-funding_tx.c common: move some files out of lightningd/ 2017-08-29 17:54:14 +02:00
run-key_derive.c common: move some files out of lightningd/ 2017-08-29 17:54:14 +02:00