diff options
| author | Ava Chow <github@achow101.com> | 2024-05-09 11:55:15 -0400 |
|---|---|---|
| committer | Ava Chow <github@achow101.com> | 2024-05-09 11:55:15 -0400 |
| commit | 921c61e9a5c8592cc9e07986612d3f4f31d663fc (patch) | |
| tree | d7c8e36744c9a80517e89b8a831d10afd753c87c /test/functional/feature_versionbits_warning.py | |
| parent | 6f1d9064381d834b0f8daa9011f18ba40834d85a (diff) | |
| parent | b259b0e8d360726b062c4b0453d1cf5a68e1933f (diff) | |
Merge bitcoin/bitcoin#29973: test: Assumeutxo: ensure failure when importing a snapshot twice
b259b0e8d360726b062c4b0453d1cf5a68e1933f [Test] Assumeutxo: ensure failure when importing a snapshot twice (Alfonso Roman Zubeldia)
Pull request description:
I am getting familiar with the `assume_utxo` tests and I found that the scenario of trying to activate a snapshot twice is not covered. This test is to ensure failure when loading a snapshot if there is already a snapshot-based chainstate.
ACKs for top commit:
fjahr:
Code review ACK b259b0e8d360726b062c4b0453d1cf5a68e1933f
kevkevinpal:
tACK [b259b0e](https://github.com/bitcoin/bitcoin/pull/29973/commits/b259b0e8d360726b062c4b0453d1cf5a68e1933f)
achow101:
ACK b259b0e8d360726b062c4b0453d1cf5a68e1933f
rkrux:
tACK [b259b0e](https://github.com/bitcoin/bitcoin/pull/29973/commits/b259b0e8d360726b062c4b0453d1cf5a68e1933f)
Tree-SHA512: 3510861390d0e40cdad6861b728df04827a1b63e642f3d956aee66ed2770b1cb7e3aa3eb00c62eb9da0544703c943cc5296936c9ebfcac18c719741c354421bb
Diffstat (limited to 'test/functional/feature_versionbits_warning.py')
0 files changed, 0 insertions, 0 deletions