----- Original Message -----
From: "Pablo Galindo Salgado" <pablogsal@gmail.com> To: "Python Dev" <python-dev@python.org> Sent: Tuesday, December 3, 2019 10:14:01 PM Subject: [Python-Dev] Multiple reference leaks in master
Hi,
Me (and Victor) have not been able to attend the buildbots for a while unfortunately and today I was checking them out after some fixes to the SSL tests and sadly the refleaks buildbots have many independent issues. At least these tests are failing due to reference leaks:
test__xxsubinterpreters, test_atexit, test_capi, test_httpservers, test_threading
I am trying to slowly fix them but finding them and debugging often takes several hours per leak. I was tracking them in https://bugs.python.org/issue38962 until I discover that there are multiple sources of leaks so I may open more issues.
Please, when you merge a PR, take a look at the buildbots (especially the refleak buildbots that do not report still to the PR in case of failure) so the issues don't keep piling up, as multiple refleaks together are much difficult to deal with.
Thanks, everyone!
Regards from cloudy London, Pablo Galindo Salgado
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/6DWAFYZG... Code of Conduct: http://python.org/psf/codeofconduct/
Also noting here that the reference leaks builds are triggered once a day so many times it's not possible to find the commit that triggered a leak through the web ui of buildbot. In this case it's good to also check the previous builds of the same worker to figure out what changed. -- Regards, Charalampos Stratakis Software Engineer Python Maintenance Team, Red Hat