You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
3.9only security fixes3.10only security fixes3.11bug and security fixesstdlibPython modules in the Lib dirtype-bugAn unexpected behavior, bug, or error
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2021-08-22.18:18:44.462>created_at=<Date2021-08-19.11:58:46.197>labels= ['type-bug', 'library', '3.9', '3.10', '3.11']
title='Method stopTestRun() is not always called for skipped tests'updated_at=<Date2021-08-22.18:18:44.462>user='https://github.com/serhiy-storchaka'
Method startTestRun() is always called for the TestResult object implicitly created by TestCase.defaultTestResult() when no TestResult object is passed to TestCase.run(). But method stopTestRun() is not always called in pair with startTestRun() for skipped tests. It is only called if SkipTest was raised directly or indirectly (via skipTest()). It is not called if a skipping decorator (@Skip, @skipIf, @skipUnless) was used for a method or a class.
New changeset a9640d7 by Serhiy Storchaka in branch 'main': bpo-44955: Always call stopTestRun() for implicitly created TestResult objects (GH-27831) a9640d7
New changeset d63114c by Miss Islington (bot) in branch '3.10': bpo-44955: Always call stopTestRun() for implicitly created TestResult objects (GH-27831) d63114c
New changeset 4e5162f by Miss Islington (bot) in branch '3.9': bpo-44955: Always call stopTestRun() for implicitly created TestResult objects (GH-27831) (GH-27882) 4e5162f
3.9only security fixes3.10only security fixes3.11bug and security fixesstdlibPython modules in the Lib dirtype-bugAn unexpected behavior, bug, or error
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: