test: raise reindex mining RPC timeout
What the developer wrote
Authored by Lőrinc
test: raise reindex mining RPC timeout
`feature_reindex.py` mines a long chain before restarting during reindex.
Bump its local RPC timeout to avoid client timeouts in parallel debug-mode runs.
What changed, and why it matters
This is a harmless test-only change. It doubles the RPC timeout in one functional test so that a slow test step (mining a long chain) does not fail due to client-side timeout during parallel debug-mode test runs. It does not change any production Bitcoin Core code, consensus rules, networking, or wallet behavior.
No action required. This is a benign test reliability fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies test/functional/feature_reindex.py only, adding self.rpc_timeout *= 2 in set_test_params(). The change increases the test framework’s wait time for RPC responses when generating a long chain before a reindex restart. There is no change to node source code, RPC server logic, validation, mempool, P2P, or any user-facing functionality.
Changed components
test/functional/feature_reindex.pyInspect captured patch +1 / −0
diff --git a/test/functional/feature_reindex.py b/test/functional/feature_reindex.py
index 1e6c1490..cf45663b 100755
--- a/test/functional/feature_reindex.py
+++ b/test/functional/feature_reindex.py
@@ -20,6 +20,7 @@ from test_framework.util import (
class ReindexTest(BitcoinTestFramework):
def set_test_params(self):
+ self.rpc_timeout *= 2 # To avoid timeout when generating the reindex chain
self.setup_clean_chain = True
self.num_nodes = 1
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.