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 their number (35 subsets): $ export SUBTEST_RANGE="[]" $ ./python -m test -m test__testcapi test_capi Then run: $ ./python -m test -m test__testcapi -R 23:23 test_capi after modifying, each time, the range of subtests to execute, with: $ export SUBTEST_RANGE="range(1,18)" # tests 1-17 result: fail $ export SUBTEST_RANGE="range(1,9)" # tests 1-8 result: pass $ export SUBTEST_RANGE="range(9,13)" # tests 9-12 result: fail $ export SUBTEST_RANGE="range(9,11)" # tests 9-10 result: fail $ export SUBTEST_RANGE="[9]" # so it must be test #9, check it now The strong limitation with this solution is that the subTest context manager must now be enclosed in a 'try except unittest.SkipTest' clause and that the context manager is used more than 100 times in the test suite. ---------- keywords: +patch Added file: http://bugs.python.org/file36875/subtest_in_range.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22607> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
