[issue22607] find by dichotomy the failing test

STINNER Victor added the comment: > See message 228968 for the rationale: http://bugs.python.org/issue22588#msg228968 Ok, this use case is now well supported by the new test.bisect tool. Yes, this issue is a duplicate of the issue #29512. I forgot this old issue! -- resolution: ->

[issue22607] find by dichotomy the failing test

Serhiy Storchaka added the comment: Wasn't the similar feature implemented in issue29512? -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue22607] find by dichotomy the failing test

Xavier de Gaye added the comment: This new version of the patch uses a specific exception to skip tests and fixes a bug when invoking the overriden and wrapped subTest method. -- Added file: http://bugs.python.org/file36994/regrest_XY_options_2.patch

[issue22607] find by dichotomy the failing test

Xavier de Gaye added the comment: The attached patch adds the '-X' and '-Y' options to the regrtest tool, allowing to select a range of tests and a range of their subtests. The patch is missing the test cases for the moment. Limitation: Does not work very well with nested subtest (nested

[issue22607] find by dichotomy the failing test

Terry J. Reedy added the comment: I believe the goal, and a better title, is Automate leak discovery within a group of tests. Bisection or dichotomy is a means, not a goal, and should not be part of the title. Leak discovery means 'find a test within the group that has a leak (which we know

[issue22607] find by dichotomy the failing test

New submission from Xavier de Gaye: This issue stems from issue 22588. See message 228968 for the rationale: Automatize the dichotomy process used to to identify memory leaks, crash, reference leak, resource leak, etc. in a failing test. -- components: Tests messages: 229067 nosy:

[issue22607] find by dichotomy the failing test

Xavier de Gaye added the comment: See msg 228968 for the rationale. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22607 ___ ___

[issue22607] find by dichotomy the failing test

Xavier de Gaye added the comment: With the attached patch (the patch does reintroduce the bug in 'test_incref_decref_API' of issue 22588 for testing purposes), it is possible to find the failing subtest rapidly: After identifying the failing test, print the list of subtests in this test and

[issue22607] find by dichotomy the failing test

Georg Brandl added the comment: I don't think this feature is generally useful enough to be included. * Since you need to modify the test code anyway (adding the try-except), it is probably just as much work to do the selection there. * Why only add selection of subtests, and not of all

[issue22607] find by dichotomy the failing test

STINNER Victor added the comment: I requested the feature because I regulary need bisect (once a month, or maybe two months). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22607 ___

[issue22607] find by dichotomy the failing test

Georg Brandl added the comment: I requested the feature because I regulary need bisect (once a month, or maybe two months). Always within subtests? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22607

[issue22607] find by dichotomy the failing test

Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22607 ___ ___

[issue22607] find by dichotomy the failing test

Xavier de Gaye added the comment: With the attached patch (the patch does reintroduce the bug in 'test_incref_decref_API' of issue 22588 for testing purposes) Sorry for not being more explicit and for being lazy doing a copy paste from msg 229022: * this is not a patch, obviously a patch

[issue22607] find by dichotomy the failing test

Xavier de Gaye added the comment: @ Georg Brandl I don't think this feature is generally useful enough to be included. * Since you need to modify the test code anyway (adding the try-except), it is probably just as much work to do the selection there. You seem to be confusing the feature

[issue22607] find by dichotomy the failing test

Georg Brandl added the comment: You seem to be confusing the feature itself with the implementation. The fact that there is an acceptable implementation is another matter (and subtest_in_range.diff is not an implementation). You yourself were calling it a solution. A feature proposal

[issue22607] find by dichotomy the failing test

Georg Brandl added the comment: Sorry for not being more explicit and for being lazy doing a copy paste from msg 229022: I see, this was split off another issue (which was already closed). I agree that a bit more verbosity in the initial description would have prevented confusion :)