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

Memleak tests #3140

Merged
merged 33 commits into from
Mar 14, 2017
Merged

Memleak tests #3140

merged 33 commits into from
Mar 14, 2017

Conversation

alex
Copy link
Member

@alex alex commented Sep 5, 2016

They don't work, because something calls OpenSSL_malloc in the subprocess before we initialize it. I assume this comes from the Binding init process

@mention-bot
Copy link

@alex, thanks for your PR! By analyzing the annotation information on this pull request, we identified @reaperhulk and @Ayrx to be potential reviewers

@alex
Copy link
Member Author

alex commented Mar 9, 2017

So, very close. For some reason it fails on py35 and py26 on windows... and the tracebacks make no sense to me.

@reaperhulk do you have opinions about how to dive in? really a pdb in there would go a long ways.

@alex
Copy link
Member Author

alex commented Mar 9, 2017

Ok, figured out py26, it was warnings on stderr. I still have absolutely no clue about py35

@alex alex modified the milestone: Nineteenth Release Mar 10, 2017
@alex
Copy link
Member Author

alex commented Mar 10, 2017

Boom, tests are green now!

@reaperhulk
Copy link
Member

Do we intend to run more substantial tests with the memory leak checks enabled in the future?

@reaperhulk reaperhulk merged commit 2e5f4ea into pyca:master Mar 14, 2017
@alex alex deleted the memleak-tests branch March 14, 2017 14:26
@alex
Copy link
Member Author

alex commented Mar 14, 2017

@reaperhulk I plan to add specific memleak tests for known historical leaks. I don't see a practical way to run our existing tests with leak checking.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants