test: change log rate limit version gate from 299900 to 290100
What changed, and why it matters
This is a one-line change in Bitcoin Core's internal test framework. It adjusts the version number at which the test suite starts passing a '-nologratelimit' option to tested nodes, lowering the gate from an unreleased future version (299900) to the actual current release series (290100). It does not change production node behavior and has no direct security relevance.
No security action required. Treat as a normal test-maintenance commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In test/functional/test_framework/test_node.py, the version gate for appending ‘-nologratelimit’ to TestNode arguments is changed from 299900 to 290100. This is purely a test-infrastructure fix to ensure functional tests exercise the no-log-rate-limit option against the correct minimum node version. The production code path for -nologratelimit is untouched.
Changed components
test/functional/test_framework/test_node.pyInspect captured patch +1 / −1
diff --git a/test/functional/test_framework/test_node.py b/test/functional/test_framework/test_node.py
index 1ec2fe8a..3b55b915 100755
--- a/test/functional/test_framework/test_node.py
+++ b/test/functional/test_framework/test_node.py
@@ -161,7 +161,7 @@ class TestNode():
self.args.append("-logsourcelocations")
if self.version_is_at_least(239000):
self.args.append("-loglevel=trace")
- if self.version_is_at_least(299900):
+ if self.version_is_at_least(290100):
self.args.append("-nologratelimit")
# Default behavior from global -v2transport flag is added to args to persist it over restarts.
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.