-
Notifications
You must be signed in to change notification settings - Fork 38.7k
test: create default wallet in extended tests #19971
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: create default wallet in extended tests #19971
Conversation
|
Can these be fixed by adding the |
|
@jnewbery if we ditch automatic wallet creation then we could already avoid that approach. |
9df44e0 to
165b8fd
Compare
|
@jnewbery done |
|
utACK 165b8fd561 Thanks for the quick fix! |
ryanofsky
left a comment
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.
Code review ACK 165b8fd5617e4bd4d5f99586306a66f084d95d13
test/functional/feature_dbcrash.py
Outdated
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.
In commit "test: create default wallet in extended tests" (165b8fd5617e4bd4d5f99586306a66f084d95d13)
Could you add a comment here? It's unclear why you'd want to call the same function n times.
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.
That's a leftover bug from my refactor.
|
Previous version 9df44e0b97ba74b4df01e600b4c19e9d75310498 also looked good, but John's suggestion to use -wallet="" is good because it provides more consistency with other tests so they be cleaned up easier later. There are a few ways tests could conceivably create default wallets:
#15454 moved us from (1) to (2). Originally this PR used approach (3) for extended tests, now it uses (2). Probably we want to end up doing (4) |
This was omitted from bitcoin#15454
165b8fd to
a5f5374
Compare
|
Third time's a charm. |
ryanofsky
left a comment
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.
Code review ACK a5f5374. Just reverted a leftover diff since last review
glozow
left a comment
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.
utACK a5f5374
Summary: No longer create a default wallet. The default wallet will still be loaded if it exists and not other wallets were specified (anywhere, including settings.json, bitcoin.conf, and command line). Tests are updated to be started with `-wallet=` if they need the default wallet. Added test to wallet_startup.py testing that no default wallet is created and that it is loaded if it exists and no other wallets were specified. Tell users how to load or create a wallet when no wallet is loaded This is a backport of [[bitcoin/bitcoin#15454 | core#15454]] and [[bitcoin/bitcoin#19971 | core#19971]] (bug fix) Depends on D10240 Test Plan: `ninja all check check-functional-extended` Reviewers: #bitcoin_abc, Fabien Reviewed By: #bitcoin_abc, Fabien Subscribers: Fabien Differential Revision: https://reviews.bitcoinabc.org/D10243
This was omitted from #15454