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.Dismiss alert
{{ message }}
Repository navigation
Incorrect timing info when using subtests and console_output_style='times' #14412
terminal timing aggregation for subtests was keyed only by nodeid
unittest SubtestReport durations were always created with duration=0
The PR adds regression coverage for duplicate subTest() contexts and measures subtest duration at the public subTest() context-manager boundary during runtest().
Activity
Criseda commentedon May 9, 2026
Opened a fix for this here: #14453
The issue turned out to have two parts:
nodeidSubtestReportdurations were always created withduration=0The PR adds regression coverage for duplicate
subTest()contexts and measures subtest duration at the publicsubTest()context-manager boundary duringruntest().fix: correct timing information for subtests when using console_outpu…
fix: correct timing information for subtests when using console_outpu…
Bugfix 14412 subtests timing (pytest-dev#14670)