diff options
| author | fanquake <fanquake@gmail.com> | 2023-06-29 09:36:15 +0100 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-06-29 09:51:53 +0100 |
| commit | e8543629ae4355fdba28eea974394d61a44d1071 (patch) | |
| tree | 293beb7992799569c0404a7e34120999f42e8090 /src/test/fuzz/miniscript.cpp | |
| parent | 626d3464695ed513e555371b870a5899872d723b (diff) | |
| parent | aaaa3aefbdfca1c9243057eeefdc19940e60bf18 (diff) | |
Merge bitcoin/bitcoin#27884: test: Use TestNode datadir_path or chain_path where possible
aaaa3aefbdfca1c9243057eeefdc19940e60bf18 test: Use TestNode *_path properties where possible (MarcoFalke)
dddd89962b26b5593860d016586ee8feb5aeea24 test: Allow pathlib.Path as RPC argument via authproxy (MarcoFalke)
fa41614a0abc05cbfbf76d6af3a186ab8d79c3f2 scripted-diff: Use wallets_path and chain_path where possible (MarcoFalke)
fa493fadfb0ac73b7c0ee308f6623213702ae6f4 test: Use wallet_dir lambda in wallet_multiwallet test where possible (MarcoFalke)
Pull request description:
It seems inconsistent, fragile and verbose to:
* Call `get_datadir_path` to recreate the path that already exists as field in TestNode
* Call `os.path.join` with the hardcoded chain name or `self.chain` to recreate the TestNode `chain_path` property
* Sometimes even use the hardcoded node dir name (`"node0"`)
Fix all issues by using the TestNode properties.
ACKs for top commit:
willcl-ark:
re-ACK aaaa3aefbdfca1c9243057eeefdc19940e60bf18
theStack:
Code-review ACK aaaa3aefbdfca1c9243057eeefdc19940e60bf18 🌊
Tree-SHA512: e4720278085beb8164e1fe6c1aa18f601558a9263494ce69a83764c1487007de63ebb51d1b1151862dc4d5b49ded6162a5c1553cd30ea1c28627d447db4d8e72
Diffstat (limited to 'src/test/fuzz/miniscript.cpp')
0 files changed, 0 insertions, 0 deletions