Closed twshelton closed 3 years ago
it will spawn btcd and lnd itself so maybe it's the docker aspect that is interfering?
I have another project for using docker but it hasn't been integrated yet: https://github.com/alexbosworth/ln-docker-daemons
I have shut down the docker processes and receive the same errors.
Another thing I would check on is your path, like which btcd
and which lnd
to make sure the go binaries can be found in test execution
ah, ok ... since those are running in Docker, I don't have the binaries locally. This PR is simply exporting a reference to a method in the the lightning package. I have BTC/LND running in docker version and also on raspiblitz. Could I simply run the tests from inside one of those environments?
I'm not sure what you are writing but if you are writing something for the lightning
package, the model there instead is to just use unit tests which don't require btcd/lnd
Otherwise I think you could use docker in various different ways but I'm not really a docker expert so not sure how to deploy it
I was able to get the tests to run in the lightning package ... all good there. I'll experiment with a couple of different options and see what I can find.
I added the integration test here: https://github.com/alexbosworth/ln-service/blob/master/test/integration/test_get_wallet_status.js
Much appreciated!!!!
I'm working on a PR for this repo and haven't been able to get the tests to run successfully. Running the wallet-integration-tests results in this for all the tests:
I'm running an M1 Macbook with BTCD/LND running in docker.
Any thoughts?
` `` FAIL test/walletrpc-integration/test_sign_psbt.js ✖ spawn btcd ENOENT
test: TAP at: line: 269 column: 19 file: internal/child_process.js function: Process.ChildProcess._handle.onexit errno: -2 code: ENOENT syscall: spawn btcd path: btcd spawnargs: