Add logs to flaky force_close_ln_dlc_channel test
#929
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This test can hang on CI. From the logs we do see a message corresponding to line 93 (where we mine one block), so it should be sufficient to log everything after that in order to identify where we are hanging.
klochowicz
approved these changes
Jul 11, 2023
|
Alright, let's merge this and test it passively. |
|
bors r+ |
|
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This test can hang on CI. From the logs we do see a message corresponding to line 93 (where we mine one block), so it should be sufficient to log everything after that in order to identify where we are hanging.
Related to #807.
We don't need to merge this. I just want to keep re-triggering the relevant job to reproduce the hang with extra context.