The generate RPCs are special in that they should only be called by the test framework itself. This way, they will call the sync function on the nodes, which can avoid intermittent test issues. Also, when the sync is disabled, it will happen explicitly by setting the sync_fun.
Apply this rule here, so that all generate calls are written consistently.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/31403.
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | rkrux, hodlinator, i-am-yuvi |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
No conflicts as of last run.
324@@ -325,7 +325,7 @@ def test_reorgs(self):
325 dusty_tx, _ = self.create_ephemeral_dust_package(tx_version=3)
326 assert_raises_rpc_error(-26, "min relay fee not met", self.nodes[0].sendrawtransaction, dusty_tx["hex"])
327
328- block_res = self.nodes[0].rpc.generateblock(self.wallet.get_address(), [dusty_tx["hex"]])
329+ block_res = self.generateblock(self.nodes[0], self.wallet.get_address(), [dusty_tx["hex"]], sync_fun=self.no_op)
0sync_fun=self.no_op
Note for myself and other reviewers: Syncing is not done in this test because the nodes are disconnected on line 321 and hence, syncing all the nodes would result in assertion errors.
0 File "/Users/rkrux/projects/bitcoin/test/functional/test_framework/test_framework.py", line 769, in sync_blocks
1 assert (all([len(x.getpeerinfo()) for x in rpc_connections]))
2 ~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3AssertionError
This way, they will call the sync function on the nodes, which can avoid intermittent test issues.
Guessing this is a proactive cleanup?
tACK fa6e599cf9fbacb393ac17e0a1b3572f217817f0
wallet_migration.py test fails on my system but I see there’s an issue for it already here: https://github.com/bitcoin/bitcoin/issues/31447
ACK fa6e599cf9fbacb393ac17e0a1b3572f217817f0
Noticed how the calls were made through .rpc. while reviewing #30239 and thought that it was a neat way to express the “same thing” in a minimally terser way. :sweat_smile:
One could probably decrease the likelyhood of rogue invalid_call=False-calls creeping back in through a change like:
0- def generatetoaddress(self, *args, invalid_call, **kwargs):
1- assert not invalid_call
2+ def generatetoaddress(self, *args, called_by_framework, **kwargs):
3+ assert called_by_framework, "Should only be called by BitcoinTestFramework itself, not subclasses. Enforces syncing of nodes in order to stabilize tests."
One could probably decrease the likelyhood of rogue
invalid_call=False-calls creeping back in through a change like:
Looks good. I am happy to review such a change. My recommendation would be to reword it a bit, so that the solution to the problem is explained at the same time: Direct call of this mining RPC is discouraged. Please use one of the self.generate* methods on the test framework, which sync the nodes to avoid intermittent test issues. You may use sync_fun=self.no_op to disable the sync explicitly.
Tested ACK fa6e599cf9fbacb393ac17e0a1b3572f217817f0
In summary, this change would generate RPCs similarly to the previous implementation, but with a key difference: when called by the test framework, it would automatically trigger the sync function. This approach helps prevent intermittent test failures by ensuring consistent node synchronization.