This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients vstinner
Date 2017-02-09.11:46:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486640763.77.0.630012847727.issue29512@psf.upfronthosting.co.za>
In-reply-to
Content
It would be great to be able to list which methods cause a reference leak.

Example right now on the 3.6 branch:
----
$ ./python -m test -R 3:3 test_os 
Run tests sequentially
0:00:00 [1/1] test_os
beginning 6 repetitions
123456
......
test_os leaked [124, 124, 124] references, sum=372
test_os leaked [114, 114, 114] memory blocks, sum=342
test_os failed in 32 sec

1 test failed:
    test_os

Total duration: 32 sec
Tests result: FAILURE
----

Which methods caused the refleak?

Is it possible to list test methods of a test file using unittest?
History
Date User Action Args
2017-02-09 11:46:03vstinnersetrecipients: + vstinner
2017-02-09 11:46:03vstinnersetmessageid: <1486640763.77.0.630012847727.issue29512@psf.upfronthosting.co.za>
2017-02-09 11:46:03vstinnerlinkissue29512 messages
2017-02-09 11:46:03vstinnercreate