These tests give additional coverage to RPCs that use conf_target in a meaningful way that doesn't just return min rates.
Inspired by https://github.com/bitcoin/bitcoin/issues/18240
These tests give additional coverage to RPCs that use conf_target in a meaningful way that doesn't just return min rates.
Inspired by https://github.com/bitcoin/bitcoin/issues/18240
Probably a good idea to stick this test somewhere else, but that would require either replication of this test(filling out the estimator?) or refactoring it to use it as a library.
one build failing:
assert_fee_amount(tx2_info["fee"], tx2_info["vsize"], med_fee)
File "/home/travis/build/bitcoin/bitcoin/build/bitcoin-x86_64-pc-linux-gnu/test/functional/test_framework/util.py", line 39, in assert_fee_amount
raise AssertionError("Fee of %s BTC too low! (Should be %s BTC)" % (str(fee), str(target_fee)))
AssertionError: Fee of 0.00008981 BTC too low! (Should be 0.00012702 BTC)
Will investigate
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
not taking this further, someone else can pick it up
@instagibbs I wrote/am writing conf_target tests as part of follow-ups to #11413 and will look at pulling these commits in.