diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-07-03 13:49:59 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-07-03 13:50:08 +0200 |
| commit | 38fbb575e25245a1b119669e56f930acaf77ec81 (patch) | |
| tree | d03b5191b4b399f9391871073e8c9700acd18646 /src/uint256.cpp | |
| parent | 7f985d6c8159f377b685ec2f404f733bdae6ac58 (diff) | |
| parent | faa1e0fb1712b1f94334e42794163f79988270fd (diff) | |
| download | bitcoin-38fbb575e25245a1b119669e56f930acaf77ec81.tar.xz | |
Merge #16294: qt: test: Create at most one testing setup
faa1e0fb1712b1f94334e42794163f79988270fd qt: test: Create at most one testing setup (MarcoFalke)
Pull request description:
It is assumed that ideally only one BasicTestingSetup exists at any point in time for each process (due to use of globals).
This assumption is violated in the GUI tests, as a testing setup is created as the first step of the `main` function and then (sometimes) another one for the following test cases.
So, the gui tests create two testing setups:
* `BasicTestingSetup` in `main` (added in fa4a04a5a942d582c62773d815c7e1e9897975d0)
* a testing setup for individual test cases
Avoid that by destructing the testing setup in main after creation and then move the explicit `ECC_Stop` to the only places where it is needed (before and after `apptests`).
ACKs for top commit:
laanwj:
code review ACK faa1e0fb1712b1f94334e42794163f79988270fd
Tree-SHA512: b8edceb7e2a8749e1de3ea80bc20b6fb7d4390bf366bb9817206ada3dc8669a91416f4803c22a0e6c636c514e0c858dcfe04523221f8851b10deaf472f107d82
Diffstat (limited to 'src/uint256.cpp')
0 files changed, 0 insertions, 0 deletions