Christian Decker 55d2e4b1d0 pytest: Spawn a new bitcoind for each test ...

Since we seem to have some isolation concerns when re-generating the
same HSM secret and re-parsing the blockchain some blocks in the past.

This also alleviates the problem of printing to a logging stream that
has been closed. Previously bitcoind would keep running despite a test
had failed and continue logging to the, now closed, StringIO that
py.test uses when capturing stdout.

The performance impact seems to be 1-3 second per test, not too bad
IMHO for increased test isolation and cleaner logs:

|--------------------+---------------+----------|
|                    | No_valgrind   | Valgrind |
|--------------------+---------------+----------|
| bitcoind per suite | 10 min 24 sec | 46:15.31 |
| bitcoind per test  | 11 min 38 sec | 49:21.64 |
|--------------------+---------------+----------|

Signed-off-by: Christian Decker <decker.christian@gmail.com>

2018-01-10 03:52:46 +00:00

..

benchmark.py

tests: prepare for bitcoind 0.16.

2017-11-28 12:15:22 +01:00

requirements.txt

pytest: Using python-bitcoinlib instead of python-bitcoinrpc

2017-01-23 10:37:34 +01:00

test_lightningd.py

pytest: Spawn a new bitcoind for each test

2018-01-10 03:52:46 +00:00

utils.py

pytest: Avoid leaking stdout fds

2018-01-08 14:36:33 +01:00