DisconnectedBlockTransactions::LimitMemoryUsage() has unit test coverage, but the default value end to end doesn’t have coverage.
This test adds exercised coverage of memory limiting of the disconnect pool, and some basic behavior sanity checks.
Another test added is making sure chainlimits are being respected on reorg, and the expected transactions pruned.
Lastly, fix the existing test case which was using a deficient test via directly inducing reorgs with invalidateblock
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/32516.
See the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Possible typos and grammar issues:
97@@ -97,6 +98,53 @@ def transaction_graph_test(self, size, n_tx_to_mine=None, fee=100_000):
98 assert_equal(entry['ancestorcount'], k + 1)
99 assert_equal(entry['ancestorsize'], sum(tx_size[0:(k + 1)]))
100
101+ self.generate(self.nodes[0], 1)
102+ assert_equal(self.nodes[0].getrawmempool(), [])
103+ wallet.rescan_utxos()
104+
105+ # Make 200 outputs to spend via wallet
106+ wallet.send_self_transfer_multi(from_node=self.nodes[0], num_outputs=200)
Not exactly sure if this is what you are asking, but: new blocks with coinbase transaction outputs for MiniWallet can be generated by passing an instance of the latter to self.generate (instead of the node object), i.e. in this case:
0 self.generate(wallet, 300)
(added +100 to let the coins mature)
🚧 At least one of the CI tasks failed.
Task lint: https://github.com/bitcoin/bitcoin/runs/42311652764
LLM reason (✨ experimental): The CI failure is due to lint errors identified by ruff.
Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:
Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.
A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.
An intermittent issue.
Leave a comment here, if you need help tracking down a confusing failure.
128+ large_std_txs = []
129+ # Add children to ensure they're recursively removed if disconnectpool trimming of parent occurs
130+ small_child_txs = []
131+ aggregate_serialized_size = 0
132+ while aggregate_serialized_size < MAX_DISCONNECTED_TX_POOL_BYTES:
133+ # Mine parents in FIFO order via priority (priority map wiped during reorg)
196@@ -190,7 +197,7 @@ def test_chainlimits_exceeded(self):
197
198 def run_test(self):
199 # Use batch size limited by DEFAULT_ANCESTOR_LIMIT = 25 to not fire "too many unconfirmed parents" error.
This comment is outdated, because DEFAULT_ANCESTOR_LIMIT = 25 is no longer after the last commit. Not sure about the reason why it was used before, is it no longer valid?
Also, changing DEFAULT_ANCESTOR_LIMIT to 100 could be mentioned in the commit message, it also affects the other subtests.
The current test directly uses invalidatblock to trigger
mempool re-entry of transactions. Unfortunately, the
behavior doesn't match what a real reorg would look like. As
a result you get surprising behavior such as the mempool
descendant chain limits being exceeded, or if a fork is
greater than 10 blocks deep, evicted block transactions stop
being submitted back into in the mempool.
Fix this by preparing an empty fork chain, invalidating that
via rpc, and then continuing with the logic, finally
reconsidering the fork chain once the rest of the test is
prepared. This triggers a more typical codepath.
Also, extend the descendant limit to 100, like ancestor
limit.
tACK 2b202e9db56487e658fc41089178f31ef4259a0d
DisconnectTip() & reconnect via invalidateblock and reconsiderblockLimitMemoryUsage(): exercised by flooding > 20 MBtest_chainlimits_exceededLogs
02025-05-21T16:57:42.023000Z TestFramework (INFO): PRNG seed is: 4085491027579870526
12025-05-21T16:57:42.024000Z TestFramework (INFO): Initializing test directory /var/folders/jb/wlbrz0t95vl58wzxjt75wqmh0000gn/T/bitcoin_func_test_jb27si_k
22025-05-21T16:57:42.337000Z TestFramework (INFO): Creating 100 transactions...
32025-05-21T16:57:42.717000Z TestFramework (INFO): The batch of 25 transactions has been accepted into the mempool.
42025-05-21T16:57:42.722000Z TestFramework (INFO): All of the transactions from the current batch have been mined into a block.
52025-05-21T16:57:44.161000Z TestFramework (INFO): The batch of 25 transactions has been accepted into the mempool.
62025-05-21T16:57:44.166000Z TestFramework (INFO): All of the transactions from the current batch have been mined into a block.
72025-05-21T16:57:46.466000Z TestFramework (INFO): The batch of 25 transactions has been accepted into the mempool.
82025-05-21T16:57:46.472000Z TestFramework (INFO): All of the transactions from the current batch have been mined into a block.
92025-05-21T16:57:48.423000Z TestFramework (INFO): The last batch of 25 transactions has been accepted into the mempool.
102025-05-21T16:57:48.571000Z TestFramework (INFO): All of the recently mined transactions have been re-added into the mempool in 0.1478879451751709 seconds.
112025-05-21T16:57:48.571000Z TestFramework (INFO): Checking descendants/ancestors properties of all of the in-mempool transactions...
122025-05-21T16:57:48.633000Z TestFramework (INFO): Creating independent transactions to test MAX_DISCONNECTED_TX_POOL_BYTES limit during reorg
132025-05-21T16:57:53.509000Z TestFramework (INFO): Check that too long chains on reorg are handled
142025-05-21T16:57:55.389000Z TestFramework (INFO): Stopping nodes
152025-05-21T16:57:55.494000Z TestFramework (INFO): Cleaning up /var/folders/jb/wlbrz0t95vl58wzxjt75wqmh0000gn/T/bitcoin_func_test_jb27si_k on exit
162025-05-21T16:57:55.494000Z TestFramework (INFO): Tests successful