diff options
| author | laanwj <126646+laanwj@users.noreply.github.com> | 2022-04-05 15:28:01 +0200 |
|---|---|---|
| committer | laanwj <126646+laanwj@users.noreply.github.com> | 2022-04-05 15:38:14 +0200 |
| commit | f421de5be611f874a027392d5fee7e113dce4f54 (patch) | |
| tree | 8ee142442db936bf40f29532f691e6e9f98f623d /test/README.md | |
| parent | ee9af95f095474641400469a2940e0fd4a052ca3 (diff) | |
| parent | fa9112aac07dc371bfda437d40eb1b841f36f392 (diff) | |
| download | bitcoin-f421de5be611f874a027392d5fee7e113dce4f54.tar.xz | |
Merge bitcoin/bitcoin#24236: Remove utxo db upgrade code
fa9112aac07dc371bfda437d40eb1b841f36f392 Remove utxo db upgrade code (MarcoFalke)
Pull request description:
It is not possible to upgrade Bitcoin Core pre-segwit (pre-0.13.1) to a recent version without a full IBD from scratch after commit 19a56d1519fb493c3e1bd5cad55360b6b80fa52b (released in version 22.0).
Any Bitcoin Core version with the new database format after commit 1088b02f0ccd7358d2b7076bb9e122d59d502d02 (released in version 0.15), can upgrade to any version that is supported as of today.
This leaves the versions 0.13.1-0.14.x. Even though those versions are unsupported, some users with an existing datadir may want to upgrade to a recent version. However, it seems reasonable to simply ask them to `-reindex` to run a full IBD from scratch. This allows us to remove the utxo db upgrade code.
ACKs for top commit:
Sjors:
re-ACK fa9112aac07dc371bfda437d40eb1b841f36f392
laanwj:
Code review ACK fa9112aac07dc371bfda437d40eb1b841f36f392
Tree-SHA512: 4243bb35df9ac4892f9fad30fe486d338745952bcff4160bcb0937c772d57b13b800647da14695e21e3655e85ee0d95fa3dc7789ee309d59ad84f422297fecb8
Diffstat (limited to 'test/README.md')
| -rw-r--r-- | test/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/README.md b/test/README.md index 87a3acb768..84264277f7 100644 --- a/test/README.md +++ b/test/README.md @@ -98,7 +98,7 @@ test/functional/test_runner.py --extended In order to run backwards compatibility tests, download the previous node binaries: ``` -test/get_previous_releases.py -b v22.0 v0.21.0 v0.20.1 v0.19.1 v0.18.1 v0.17.2 v0.16.3 v0.15.2 +test/get_previous_releases.py -b v22.0 v0.21.0 v0.20.1 v0.19.1 v0.18.1 v0.17.2 v0.16.3 v0.15.2 v0.14.3 ``` By default, up to 4 tests will be run in parallel by test_runner. To specify |