diff options
| author | merge-script <fanquake@gmail.com> | 2025-03-21 16:46:54 +0800 |
|---|---|---|
| committer | merge-script <fanquake@gmail.com> | 2025-03-21 16:46:54 +0800 |
| commit | 2db00278ea571d0f734609f9fefecfa75c16ee34 (patch) | |
| tree | 0423db3b928de8e191c432160d52df588a2127e9 /test/lint/lint-python-dead-code-whitelist | |
| parent | c9a61509ba3eee3308f97bd9531a817a3d5cca08 (diff) | |
| parent | 63b534f97e591d4e107fd5148909852eb2965d27 (diff) | |
Merge bitcoin/bitcoin#31910: qa: fix an off-by-one in utxo snapshot fuzz target and sanity check its snapshot data
63b534f97e591d4e107fd5148909852eb2965d27 fuzz: sanity check hardcoded snapshot in utxo_snapshot target (Antoine Poinsot)
3b85eba83abe561078c91f5a5c49cf26c682c19b test util: split up ConnectBlock from MineBlock (Antoine Poinsot)
d1527f6b88656ff4aab3c671c6d9780ea2ae986e qa: correct off-by-one in utxo snapshot fuzz target (Antoine Poinsot)
Pull request description:
The assumeutxo data for the fuzz target could change and invalidate the hash silently, preventing the fuzz target from reaching some code paths. Fix this by introducing a unit test which would break if the snapshot data the fuzz target relies on were to change.
In implementing this i noticed the height used for coins in the fuzz target is actually off-by-one (as if the first block in the created chain was the genesis but it's block `1`), so fix that too.
ACKs for top commit:
mzumsande:
Code Review ACK 63b534f97e591d4e107fd5148909852eb2965d27
fjahr:
tACK 63b534f97e591d4e107fd5148909852eb2965d27
Tree-SHA512: 2399b6e74db9b78aab8efba67c57a405d2d7d880ae3b7d8518a1c96cc6266f61f5e77722cd999adeac5d3e03e73d84cf9ae7bdbcc0afae198cc87049dde4012f
Diffstat (limited to 'test/lint/lint-python-dead-code-whitelist')
0 files changed, 0 insertions, 0 deletions