• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In
Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.
New Repo Setting:
INCLUDE COVERAGE % WITH WARNINGS ABOUT DRIFTED BUILDS?

Enabling this setting will include a (potentially inaccurate) coverage % with warning messages in status updates for drifted builds.

Adjust setting

lightninglabs / taproot-assets / 13433676818
55%
main: 47%

Build:
Build:
LAST BUILD BRANCH: test/custom_channels_move
DEFAULT BRANCH: main
Ran 20 Feb 2025 10:58AM UTC
Jobs 2
Files 253
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Feb 2025 10:49AM UTC coverage: 54.416% (+0.02%) from 54.4%
13433676818

Pull #1402

github

guggero
tapfreighter: create anchor output keys correctly

Once we have multiple asset IDs (and with that multiple distinct virtual
packets), we need to make sure that we create our anchor outputs
correctly.
We need to make sure that the anchor outputs for the same index are
actually the same (e.g. same internal key). If we just blindly loop over
them and assign new keys, then two virtual outputs that reference the
same anchor output index would have different keys and we'd fail a check
then attempting to commit those packets to a BTC anchor transaction.
Pull Request #1402: [wallet]: refactor in preparation for group key channel funding

389 of 631 new or added lines in 11 files covered. (61.65%)

66 existing lines in 10 files now uncovered.

48712 of 89517 relevant lines covered (54.42%)

0.8 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
1
80.68
0.01% tapsend/send.go
2
0.0
0.0% tapchannelmsg/custom_channel_data.go
7
80.83
1.06% tapfreighter/wallet.go
10
64.29
-35.71% fn/memory.go
32
63.61
-0.07% rpcserver.go
43
58.79
-3.4% tapgarden/mock.go
65
4.01
-0.0% tapchannel/aux_funding_controller.go
82
77.6
tapfreighter/fund.go

Uncovered Existing Lines

Lines Coverage ∆ File
2
72.65
0.0% asset/group_key.go
3
63.61
-0.07% rpcserver.go
3
58.79
-3.4% tapgarden/mock.go
5
79.74
-0.3% asset/asset.go
5
4.01
-0.0% tapchannel/aux_funding_controller.go
5
43.08
-0.35% tapchannel/aux_leaf_signer.go
6
75.54
-0.54% tapgarden/custodian.go
8
77.14
-0.38% tapgarden/caretaker.go
11
70.55
-1.6% asset/mock.go
18
86.93
-11.76% address/mock.go
Jobs
ID Job ID Ran Files Coverage
1 itest - 13433676818.1 20 Feb 2025 11:06AM UTC 248
47.48
GitHub Action Run
2 unit - 13433676818.2 20 Feb 2025 10:58AM UTC 253
27.75
GitHub Action Run
Source Files on build 13433676818
  • Tree
  • List 253
  • Changed 32
  • Source Changed 0
  • Coverage Changed 32
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #1402
  • PR Base - main (#13426236628)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc