This isn't always super useful because the tests assume a fresh node each time, but gives us the ability to run all or specific tests against some external ndoe at least.
To avoid ctests conflicting you'll need to use --test-threads 1. You'll still see some failures because a few tests will assume a fresh state and then update it.
This isn't always super useful because the tests assume a fresh node each time, but gives us the ability to run all or specific tests against some external ndoe at least.
To avoid ctests conflicting you'll need to use
--test-threads 1. You'll still see some failures because a few tests will assume a fresh state and then update it.