[issue25753] Reference leaks in test_smtplib

2020-02-12 Thread Dong-hee Na
Dong-hee Na added the comment: +1 for me to close this issue. On the master branch, this issue is not reproducible. I am closing this issue, if someone wants to open this issue, please re-open this :) -- nosy: +corona10 resolution: -> out of date stage: -> resolved status: open -> c

[issue25753] Reference leaks in test_smtplib

2020-02-07 Thread hai shi
hai shi added the comment: > I cannot reproduce these leaks. I think this issue should be closed. +1, I have run 15+ times in my vm but not found these leaks:( -- nosy: +shihai1991 ___ Python tracker __

[issue25753] Reference leaks in test_smtplib

2019-09-10 Thread Zackery Spytz
Zackery Spytz added the comment: I cannot reproduce these leaks. I think this issue should be closed. -- nosy: +ZackerySpytz ___ Python tracker ___ ___

[issue25753] Reference leaks in test_smtplib

2016-01-14 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: The result of searching leaks is not stable. I ran the test 10 times and got failures 3 times. -- ___ Python tracker ___

[issue25753] Reference leaks in test_smtplib

2016-01-14 Thread SilentGhost
SilentGhost added the comment: Serhiy, I cannot reproduce these leaks on recent checkout. Is this something that's still happens for you? -- nosy: +SilentGhost ___ Python tracker __

[issue25753] Reference leaks in test_smtplib

2015-11-27 Thread Serhiy Storchaka
New submission from Serhiy Storchaka: $ ./python -m test.regrtest -uall -R 3:3 test_smtplib [1/1] test_smtplib beginning 6 repetitions 123456 .. test_smtplib leaked [0, 1, 1] references, sum=2 test_smtplib leaked [0, 1, 2] memory blocks, sum=3 1 test failed: test_smtplib -- compo