-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core-lightning: restart bitcoind when we're restarted. #52
Conversation
This restores previous behavior (we had bugs, so we just changed to restarting it every time). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
I found a similar race in our core-lightning CI: when a node restarts, there's a race where another node could start on the same port. In this case, we catch the exception, which was covering up the failure. The test then talks to the wrong bitcoind, which has unpredictable results. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
ee6e5f0
to
cc020d4
Compare
The only regression that we have with this PR is the execution time of the test, In particular:
I will check this in local and see what is going on! |
See final fixup commit! If we don't rewrite the bitcoin.conf when we change port, it all breaks... |
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Closing in favor of #53 that includes a patch of this patch. In addition, the CI now run @niftynei cln patch ElementsProject/lightning#5367 so we start to monitoring other CI failure, but at the moment this problem looks fixed |
Nobody else seems to, which explains some of our issues?
No, still failing. Let me add a crapton of logging, since it only fails on GH!
Fixes #31