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 python-dev, skrah, vstinner, xdegaye
Date 2014-10-10.08:39:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412930384.95.0.64145009963.issue22588@psf.upfronthosting.co.za>
In-reply-to
Content
> That was really fast Victor!

I modified test_capi to only run one testcase, and I modified the testcase which caused the issue to run a subset of tests. By dichotomy, I found that only one function caused the fatal error.

Does anyone know how to automatize the dichotomy process? Maybe I should open a new issue for this?

It's very boring to disable tests by modifying the source code.

It would help a lot to identify memory leaks, crash, reference leak, resource leak, etc.
History
Date User Action Args
2014-10-10 08:39:44vstinnersetrecipients: + vstinner, skrah, xdegaye, python-dev
2014-10-10 08:39:44vstinnersetmessageid: <1412930384.95.0.64145009963.issue22588@psf.upfronthosting.co.za>
2014-10-10 08:39:44vstinnerlinkissue22588 messages
2014-10-10 08:39:44vstinnercreate