-
Notifications
You must be signed in to change notification settings - Fork 940
lnprototest: updating and patch lnprototest #5372
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
lnprototest: updating and patch lnprototest #5372
Conversation
@rustyrussell There is some failure related to the gossip test, but this looks like that we can cover in lnprototest? or maybe we did already https://github.com/rustyrussell/lnprototest/blob/master/tests/test_bolt7-01-channel_announcement-success.py
I'm pretty sure that if I restart it I will have the test happy, but maybe we can hide this failure |
I have a separate fix for this, so restarting... |
If we can't broadcast the tx, confirm that it didn't end up in the mempool or the utxo set before throwing an error. Note that this doesn't protect us in the case where the funding output has already been *spent*... but that's extremely rare, right? Fixes ElementsProject#5296 Reported-By: @rustyrussell Collab-With: @vincenzopalazzo
Changelog-None: patch lnprototest Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Now that we're more broadcast failure aware, let's check that on actual broadcast failure we still update UTXO set properly and the channel opens.
cdb6ad8
to
6becf47
Compare
@vincenzopalazzo i removed your "run the lnprototests x2" patch in anticipation of getting this merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build on top of #5367
The @niftynei patch finally fixed the lnprototest failure rustyrussell/lnprototest#31 and with the stress test that I added on lnprototest CI that ran lnprototest 20 times, I found another strange failure rustyrussell/lnprototest#56 that I'm no longer able to reproduce, so I added a couple of logging call.
In addition, I enable the CI lnprototest that run the test 2 time, in this way we can try to find the bug before we fall into the lucky case forever. if we fall in the lucky case 2 time? well, we are lucky no?
let's see what the full CI tells us now, and if we finally have the CI clean!
Fixes #5148