What the developer wrote
Authored by Andras Banki-Horvath
multi: Run itests with bitcoind miner in CI
Add a basic itest matrix entry that sets minerbackend=bitcoind alongside
backend=bitcoind, ensuring CI covers the bitcoind miner path.
What changed, and why it matters
This commit only adds a new automated test configuration to the project's GitHub Actions CI workflow. It makes the test suite also run with a specific Bitcoin mining backend option (bitcoind). There are no code changes to the actual LND software, no bug fixes, and no security-related changes.
No security action needed. This is a routine CI/testing infrastructure change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies .github/workflows/main.yml to add a new matrix entry named ‘bitcoind-miner’ with args ‘backend=bitcoind minerbackend=bitcoind cover=1’. This expands CI coverage for integration tests using bitcoind as both the chain backend and the miner backend. No source code, build scripts, dependencies, or runtime behavior of lnd is changed.
Changed components
.github/workflows/main.ymlInspect captured patch +2 / −0
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index e72b3e8..0ae0192 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -280,6 +280,8 @@ jobs:
args: backend=btcd cover=1
- name: bitcoind
args: backend=bitcoind cover=1
+ - name: bitcoind-miner
+ args: backend=bitcoind minerbackend=bitcoind cover=1
- name: bitcoind-notxindex
args: backend="bitcoind notxindex"
- name: neutrino
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.