As per title
- Group Reviewers
- rSTAGINGd68bb71616a3: [qa] allow assert_fee to have a bit more wiggleroom
rABCd68bb71616a3: [qa] allow assert_fee to have a bit more wiggleroom
make check && ./test/functional/test_runner.py
Okay, so for fundrawtransaction, when fees are dropped, the first transaction sent in a series of fee checks is with a feerate of 100sat/kb. This results in a fee of 0.00000202. This is ceiled so as to not be under the minimum relay fee. It then proceeds to calculate expected fees based on multiples of this due to the dummy signatures that get added during fundraw transaction.
However, the full fee was 0.000002016. So when it tries another transaction with a 10x feerate it expects 0.00002020 due to the previous truncation -- it then fails.
Something like this patch is needed to deal with that kind of problem. This particular method may not be best.