diff options
author | John Newbery <john@johnnewbery.com> | 2021-09-27 16:40:25 +0100 |
---|---|---|
committer | John Newbery <john@johnnewbery.com> | 2021-11-03 12:04:46 +0000 |
commit | 497c9e29640858bb3beb20089c2d4f9e133c7e42 (patch) | |
tree | 16860c100817166305f50ac35e1473b60a126234 /src/test | |
parent | baa9fc941cac76b35630da16d77fa2a8b0cc1755 (diff) |
[test] Don't set bypass_limits to true in txvalidationcache_tests.cpp
AcceptToMemoryPool() is called for transactions with fees above
minRelayTxFee and with the mempool not full, so setting bypass_limits to
true or false has no impact on the test.
The only way that changing bypass_limits from true to false could change
the result would be to change the outcome to INVALID(TX_MEMPOOL_POLICY).
Since all the ATMP calls in this test result in VALID both before and
after this change, there is no change in behavior.
Diffstat (limited to 'src/test')
-rw-r--r-- | src/test/txvalidationcache_tests.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/txvalidationcache_tests.cpp b/src/test/txvalidationcache_tests.cpp index afb3ad0cfd..f799b8c9aa 100644 --- a/src/test/txvalidationcache_tests.cpp +++ b/src/test/txvalidationcache_tests.cpp @@ -37,7 +37,7 @@ BOOST_FIXTURE_TEST_CASE(tx_mempool_block_doublespend, Dersig100Setup) LOCK(cs_main); const MempoolAcceptResult result = AcceptToMemoryPool(m_node.chainman->ActiveChainstate(), *m_node.mempool, MakeTransactionRef(tx), - true /* bypass_limits */); + false /* bypass_limits */); return result.m_result_type == MempoolAcceptResult::ResultType::VALID; }; |