| commit | 2b4ea520b717b3ca894adbac17796786667764d3 | |
| author | John Newbery <john@johnnewbery.com> | |
| Wed, 16 Aug 2017 19:46:48 +0000 (16 15:46 -0400) | ||
| committer | John Newbery <john@johnnewbery.com> | |
| Wed, 23 Aug 2017 14:56:31 +0000 (23 10:56 -0400) | ||
| tree | e879a1ca697e137363ac4350345e778588a38183 | treesnapshot (tar.gz zip) |
| parent | 31b2612bbf199fcbbb242fc1cfa2ad6221b0dcc7 | commitdiff |
[tests] fix timeout issues from TestNode
Fixes a couple of bugs from the introduction of TestNode:
- test scripts were no longer able to specify a custom timeout for
starting a node. Therefore tests with nodes that take a long time to
start up (eg pruning.py) would fail.
- the test for whether a node has failed on start up was broken
by changing 'assert x is None' to 'assert not x'. Since
subprocess.poll() can return None (indicating the node is still running)
or 0 (indicating the node exited with return code 0), this was a
regression.
Fixes a couple of bugs from the introduction of TestNode:
- test scripts were no longer able to specify a custom timeout for
starting a node. Therefore tests with nodes that take a long time to
start up (eg pruning.py) would fail.
- the test for whether a node has failed on start up was broken
by changing 'assert x is None' to 'assert not x'. Since
subprocess.poll() can return None (indicating the node is still running)
or 0 (indicating the node exited with return code 0), this was a
regression.
| test/functional/dbcrash.py | diffblobblamehistory | |
| test/functional/test_framework/test_node.py | diffblobblamehistory |