Repository navigation
--fail-fast: cancelled tests are not reported, and a failure can appear twice as an "Unhandled exception" node #7119
Description
Summary
Two reporting problems remain on --fail-fast runs after #7115.
- Extra "Unhandled exception" test node. When fail-fast stops two scheduling phases that run concurrently, the first failure is reported a second time as an extra "Unhandled exception" test node.
- Cancelled tests are not reported. Tests that fail-fast cancels before they start get no result node. A run can show
total: 1even though many tests were selected.
Repro
- Problem 2:
TUnit.TestProject --treenode-filter /*/*/KeyedNotInParallelFailFast7074/* --fail-fast --maximum-parallel-tests 1reports only the failing test. TheWaitstests that were cancelled while waiting for their slot do not appear. - Problem 1: needs fail-fast to trigger while two phases are running (for example, parallel and keyed tests at the same time).
Notes
Both predate #7084 and #7115; found while fixing the fail-fast host crash in #7115. Expected behaviour is likely that cancelled tests are reported as skipped or cancelled, and that each failure is reported exactly once.
Activity
thomhurst commentedon Oct 18, 2026
Related symptom found while investigating a CI timeout (see #7125). When the session is cancelled (for example by
--timeout), the global[NotInParallel]phase logs every remaining queued test as "Unhandled exception in test …" with aTaskCanceledExceptionfromNotInParallelLock.EnterExclusiveAsync. That made a plain timeout look like a lock deadlock. Reporting those tests as cancelled, or stopping the loop once the session token is cancelled, would fix both this and the fail-fast reporting gap above. Coordinate with #7115, which also changesTestScheduler.fix(engine): report every test once on fail-fast runs (thomhurst#7145)