-
Notifications
You must be signed in to change notification settings - Fork 406
Process_events_multithreaded
is flaky
#2385
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
Labels
Comments
TheBlueMatt
added a commit
to TheBlueMatt/rust-lightning
that referenced
this issue
Aug 19, 2024
This test was added some time ago in 0c034e9, but never made any sense. `PeerManager::process_events` will go around its loop as many times is required to ensure we've always processed all events which were pending prior to a `process_events` call, so having a test that checks that we never go around more than twice is obviously broken. And, indeed, in CI this tests fails with some regularity. Instead, the test here is changed to ensure that we detectably go around the loop again at least once. Fixes lightningdevkit#2385
TheBlueMatt
added a commit
to TheBlueMatt/rust-lightning
that referenced
this issue
Aug 19, 2024
This test was added some time ago in 0c034e9, but never made any sense. `PeerManager::process_events` will go around its loop as many times is required to ensure we've always processed all events which were pending prior to a `process_events` call, so having a test that checks that we never go around more than twice is obviously broken. And, indeed, in CI this tests fails with some regularity. Instead, the test here is changed to ensure that we detectably go around the loop again at least once. Fixes lightningdevkit#2385
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CI on latest main said:
The text was updated successfully, but these errors were encountered: