test: Change feature_config_args.py not to rely on strange regtest=0 behavior#17556
test: Change feature_config_args.py not to rely on strange regtest=0 behavior#17556maflcko merged 1 commit intobitcoin:masterfrom
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsNo conflicts as of last run. |
|
Concept ACK |
|
utACK 228fb7e |
Suggestions from MarcoFalke <[email protected]> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
Suggestions from MarcoFalke <[email protected]> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
Suggestions from MarcoFalke <[email protected]> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
|
Rebased b339f83 -> affbdfa ( |
Suggestions from MarcoFalke <[email protected]> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
…behavior Update test to simply generate a normal mainnet configuration file instead of using a crazy setup where a regtest=1 config file using an includeconf in the [regtest] section includes another config file that specifies regtest=0, retroactively switching the network to mainnet. This setup was fragile and only worked because the triggered InitError happened early enough that none of the ignored [regtest] options mattered (only affecting log output).
Suggestions from MarcoFalke <[email protected]> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
Suggestions from MarcoFalke <[email protected]> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
| return datadir | ||
|
|
||
|
|
||
| def write_config(config_path, n, chain, extra_config=""): |
There was a problem hiding this comment.
| def write_config(config_path, n, chain, extra_config=""): | |
| def write_config(config_path, *, n, chain, extra_config=""): |
nit: would be good to force named args to avoid mixing up n and chain. E.g. setting chain=0 will work, but is a confusing way to say mainnet.
There was a problem hiding this comment.
re: #17556 (comment)
nit: would be good to force named args to avoid mixing up
nandchain. E.g. settingchain=0will work, but is a confusing way to say mainnet.
Thanks, added and updated callers.
| return datadir | ||
|
|
||
|
|
||
| def write_config(config_path, n, chain, extra_config=""): |
There was a problem hiding this comment.
re: #17556 (comment)
nit: would be good to force named args to avoid mixing up
nandchain. E.g. settingchain=0will work, but is a confusing way to say mainnet.
Thanks, added and updated callers.
|
ACK ff44cae |
…on stra… …nge regtest=0 behavior
Update test to simply generate a normal mainnet configuration file instead of using a crazy setup where a regtest=1 config file using an includeconf in the [regtest] section includes another config file that specifies regtest=0, retroactively switching the network to mainnet.
This setup was fragile and only worked because the triggered InitError happened early enough that none of the ignored [regtest] options mattered (only affecting log output).
This change was originally made as part of #17493