Change Details

> [test] Don't set bypass_limits to true in txvalidatiocache_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. https://github.com/bitcoin/bitcoin/pull/23173/commits/497c9e29640858bb3beb20089c2d4f9e133c7e42 > [test] Don't set bypass_limits to true in txvalidation_tests.cpp > > AcceptToMemoryPool() is called for an invalid coinbase transaction, 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 the ATMP call in this test results in INVALID(TX_CONSENSUS) both > before and after this change, there is no change in behavior. This is a backport of core#23173 https://github.com/bitcoin/bitcoin/pull/23173/commits/4c24142b1ec121623f81ba644d77341bc1bd88dd

> [test] Don't set bypass_limits to true in txvalidatiocache_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. https://github.com/bitcoin/bitcoin/pull/23173/commits/497c9e29640858bb3beb20089c2d4f9e133c7e42 > [test] Don't set bypass_limits to true in txvalidation_tests.cpp > > AcceptToMemoryPool() is called for an invalid coinbase transaction, 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 the ATMP call in this test results in INVALID(TX_CONSENSUS) both > before and after this change, there is no change in behavior. This is a backport of [[https://github.com/bitcoin/bitcoin/pull/23173 | core#23173]] https://github.com/bitcoin/bitcoin/pull/23173/commits/4c24142b1ec121623f81ba644d77341bc1bd88dd

> [test] Don't set bypass_limits to true in txvalidatiocache_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. https://github.com/bitcoin/bitcoin/pull/23173/commits/497c9e29640858bb3beb20089c2d4f9e133c7e42 > [test] Don't set bypass_limits to true in txvalidation_tests.cpp > > AcceptToMemoryPool() is called for an invalid coinbase transaction, 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 the ATMP call in this test results in INVALID(TX_CONSENSUS) both > before and after this change, there is no change in behavior. This is a backport of [[https://github.com/bitcoin/bitcoin/pull/23173 | core#23173]] https://github.com/bitcoin/bitcoin/pull/23173/commits/4c24142b1ec121623f81ba644d77341bc1bd88dd