-
Notifications
You must be signed in to change notification settings - Fork 36.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: Change feature_config_args.py not to rely on strange regtest=0 behavior #17556
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 <falke.marco@gmail.com> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
Suggestions from MarcoFalke <falke.marco@gmail.com> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
Suggestions from MarcoFalke <falke.marco@gmail.com> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
Suggestions from MarcoFalke <falke.marco@gmail.com> 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 <falke.marco@gmail.com> 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 <falke.marco@gmail.com> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
Suggestions from MarcoFalke <falke.marco@gmail.com> bitcoin#17556 (review) - Fix comment mentioning chain name instead of subdirectory name - Switch from -regtest/-testnet options to -chain option
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
let me know whether you want to address the nit or not
return datadir | ||
|
||
|
||
def write_config(config_path, n, chain, extra_config=""): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re: #17556 (comment)
nit: would be good to force named args to avoid mixing up
n
andchain
. E.g. settingchain=0
will work, but is a confusing way to say mainnet.
Thanks, added and updated callers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return datadir | ||
|
||
|
||
def write_config(config_path, n, chain, extra_config=""): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re: #17556 (comment)
nit: would be good to force named args to avoid mixing up
n
andchain
. E.g. settingchain=0
will 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