|
Ran
|
Jobs
1
|
Files
130
|
Run time
1min
|
Badge
README BADGES
|
push
github
Merge rust-bitcoin/rust-bitcoin#2456: Use InputWeightPrediction to calculate effective_value <a class=hub.com/rust-bitcoin/rust-bitcoin/commit/<a class="double-link" href="https://git"><a class=hub.com/rust-bitcoin/rust-bitcoin/commit/f6105ea4171a85ce21443d7eb76b7aa9cadab53a">f6105ea41 Use InputWeightPrediction to calculate effective_value (yancy) Pull request description: closes: https://github.com/rust-bitcoin/rust-bitcoin/issues/2455 Also, what about moving `effective_value` to `InputWeightPrediction`? Marking as a draft until we can add api changes again. ACKs for top commit: apoelstra: ACK f6105ea4171a85ce21443d7eb76b7aa9cadab53a; successfully ran local tests; yeah, this API does look nicer Kixunil: ACK f6105ea4171a85ce21443d7eb76b7aa9cadab53a Tree-SHA512: 20592e49c11da68a6abcd11da33a6908055
8 of 8 new or added lines in 1 file covered. (100.0%)
6 existing lines in 1 file now uncovered.22556 of 26843 relevant lines covered (84.03%)
16570.68 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 6 |
85.9 |
-0.37% | bitcoin/src/psbt/mod.rs |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 14562701522.1 | 130 |
84.03 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|