Closed offerm closed 6 years ago
I haven't seen this, and I wonder if it's possibly the result of some bad data in the xud_test
database. Was this test run using the recently merged sqlite migration? That ensures that there is no stale data in databases used for tests.
not using the databases anymore. using the latest master.
can you verify this is still happening? @offerm
Don't see this problem any more. I do see some errors but the tests are passing.
for example:
P2P Sanity Tests
10/28/2018, 1:05:26 PM [LND][2] error: could not find lnd macaroon, is lnd installed?
10/28/2018, 1:05:26 PM [LND][1] error: could not find lnd macaroon, is lnd installed?
10/28/2018, 1:05:26 PM [GLOBAL][2] warn: RPC server is disabled.
10/28/2018, 1:05:26 PM [GLOBAL][1] warn: RPC server is disabled.
10/28/2018, 1:05:26 PM [P2P][2] warn: Could not verify reachability of advertised address: localhost:0
10/28/2018, 1:05:26 PM [P2P][1] warn: Could not verify reachability of advertised address: localhost:0
✓ should connect successfully
These errors are marked with red.
note: If I execute the tests when the setup is active (btcd, ltcd, lndx2, xud all running and connected) I get errors. If I stop XUD (leaving the other 4 processes running) and run the tests all is good.
@kilrau please consider if we should close it or handle it.
It's a matter of preference I think. The errors are deliberate and expected. It would be easy to silence all errors, but the output might be nice to have for diagnosing unexpected errors. But I don't think it's a big deal, I'd you think the output should be silenced we can do that.
I think we can leave the output (to catch unexpected things inf future), but not handle it for now
Running
npm run test
. All tests pass but there is an ugly error:Not sure why these nodes are not available, why we try to connect them in test, and why failure does not fail the test.
To be checked