Page MenuHomePhabricator

[qa] allow assert_fee to have a bit more wiggleroom

Authored by schancel on Oct 1 2018, 22:14.



As per title

Test Plan
make check && ./test/functional/

Diff Detail

rABC Bitcoin ABC
Lint Not Applicable
Tests Not Applicable

Event Timeline

deadalnix requested changes to this revision.Oct 2 2018, 11:24
deadalnix added a subscriber: deadalnix.

Please update the description to explain why this needs to happen.

This revision now requires changes to proceed.Oct 2 2018, 11:24

I actually ended up fixing a different cause of the failure.

This revision now requires changes to proceed.Oct 5 2018, 01:11

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.

jasonbcox requested changes to this revision.Oct 5 2018, 18:13
jasonbcox added a subscriber: jasonbcox.
jasonbcox added inline comments.
28 ↗(On Diff #5216)

Depending on how rigid the +/- 10 range is, you could include it as a parameter to this function and allow the individual tests to determine the tolerance.

34 ↗(On Diff #5216)

Update this comment and make it reflect how +/- 10 was chosen

This revision is now accepted and ready to land.Oct 8 2018, 11:56
This revision was automatically updated to reflect the committed changes.