Pablo Galindo Salgado <pablog...@gmail.com> added the comment:
> We can stop using --junit-xml if we want. GitHub Actions doesn't support > displaying test results anyway, so once Azure Pipelines is switched off we'll > just be reading the console all the time anyway (unless Buildbot has a way of > rendering test results that I haven't noticed?) We are using --junit-xml on the buildbots to analyze failures and in the future we can use it to better display the summary, as is more reliable than parsing the longs. > I guess keeping those objects around looks like a leak? Yeah, because it seems that we collect those objects in the innermost runner, while the refleak runner runs the whole "test suite" (the test file, like test_list.py) as one unit. To be honest, the easiest fix here maybe is just deactivating the --junit and make a warning as in bpo-27103 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39253> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
