Skip to content
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

pyln-testing: fix catching of memleak/broken errors at exit. #7573

Merged
merged 2 commits into from
Aug 15, 2024

Conversation

rustyrussell
Copy link
Contributor

Commit 901342b ("pyln-testing: require explicit pattern for BROKEN messages.") changed to a manual scan of logs rather than using is_in_log, so it needs to manually refresh, otherwise we miss final log messages.

This causes us to often miss memleak messages, which are printed only in the exit path!

Reported-by: Lagrang3
Fixes: #7565

Copy link
Member

@cdecker cdecker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

Once we fix our broken log detection, we find some we were missing.

Signed-off-by: Rusty Russell <[email protected]>
Commit 901342b ("pyln-testing: require
explicit pattern for BROKEN messages.") changed to a manual scan of
logs rather than using is_in_log, so it needs to manually refresh,
otherwise we miss final log messages.

This causes us to often miss memleak messages, which are printed
only in the exit path!

Reported-by: Lagrang3
Fixes: ElementsProject#7565
Signed-off-by: Rusty Russell <[email protected]>
@rustyrussell rustyrussell merged commit 395781f into ElementsProject:master Aug 15, 2024
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Is CI not checking for memory leaks?
2 participants