diff options
| author | glozow <gloriajzhao@gmail.com> | 2024-05-20 09:46:49 +0100 |
|---|---|---|
| committer | glozow <gloriajzhao@gmail.com> | 2024-05-20 09:47:31 +0100 |
| commit | ecd23656db174adef61d3bd753d02698c3528192 (patch) | |
| tree | 1e45e1e830e09d0f14f6dc30586276f8e4ba2a9a /src/crypto/sha1.cpp | |
| parent | 063bb2fbb571b9ee4940dacbf56f36b15f6aa501 (diff) | |
| parent | 8950053636cb38ed85fe2d58b53e5d0acb35c390 (diff) | |
Merge bitcoin/bitcoin#30133: test: remove unneeded `-maxorphantx=1000` settings
8950053636cb38ed85fe2d58b53e5d0acb35c390 test: remove unneeded `-maxorphantx=1000` settings (Sebastian Falbesoner)
Pull request description:
It's unclear what the motivation for increasing the orphan pool is here, and it seems that this not needed at all. None of these tests involve orphan transactions explicitly, and if they would occur occasionally, there is no good reason to prefer a value of 1000 over the default of 100 (see DEFAULT_MAX_ORPHAN_TRANSACTIONS).
ACKs for top commit:
maflcko:
utACK 8950053636cb38ed85fe2d58b53e5d0acb35c390
edilmedeiros:
Tested ACK 8950053636cb38ed85fe2d58b53e5d0acb35c390
AngusP:
tACK 8950053636cb38ed85fe2d58b53e5d0acb35c390
glozow:
ACK 8950053636cb38ed85fe2d58b53e5d0acb35c390 From skimming the tests, it appears that none of these need a larger `-maxorphantx`.
Tree-SHA512: 81d4a4fb2ea92b97119f21cbc6c4b1240d863269932e6adf4982aead9726f20652523a4707add3ad38eb332d4452de41de6735265f22e62298f3b4b45de75a57
Diffstat (limited to 'src/crypto/sha1.cpp')
0 files changed, 0 insertions, 0 deletions