diff options
| author | Ava Chow <github@achow101.com> | 2024-09-13 16:12:19 -0400 |
|---|---|---|
| committer | Ava Chow <github@achow101.com> | 2024-09-13 16:12:19 -0400 |
| commit | 87d54500bfa350c0f8c458b46ab78ea2b410978f (patch) | |
| tree | 95b0af355133cf854e62151f7227129ef16fa2c4 /src/test | |
| parent | 71af7435ef934a29d854bbe23c0e8602730ebe10 (diff) | |
| parent | 72c9a1fe94f927220d3159f516fda684ae9d4caa (diff) | |
Merge bitcoin/bitcoin#30892: test: Check already deactivated network stays suspended after dumptxoutset
72c9a1fe94f927220d3159f516fda684ae9d4caa test: Check that network stays suspended after dumptxoutset if it was off before (Fabian Jahr)
Pull request description:
Follow-up to #30817 which covered the robustness of `dumptxoutset`: network is deactivated during the run but re-activated even when an issue was encountered. But it did not cover the case if the user had deactivated the network themselves before. In that case the user may want the network to stay off so the network is not reactivated after `dumptxoutset` finishes. A test for this behavior is added here.
ACKs for top commit:
achow101:
ACK 72c9a1fe94f927220d3159f516fda684ae9d4caa
pablomartin4btc:
ACK 72c9a1fe94f927220d3159f516fda684ae9d4caa
theStack:
utACK 72c9a1fe94f927220d3159f516fda684ae9d4caa
tdb3:
tested ACK 72c9a1fe94f927220d3159f516fda684ae9d4caa
Tree-SHA512: 18a57c5782e99a018414db0597e88debeb32666712c2a75dddbb55135d8f1ddd1eeacba8bbbd35fc03b6c4ab0522fe074ec08edea729560b018f51efabf00e89
Diffstat (limited to 'src/test')
0 files changed, 0 insertions, 0 deletions