Reported single unit test as timed out lost in counting

[TomasPeer]

We use Nunit console application in CI build chain. During migration of our old projects to NET8 we noticed weird total test count where one test was reported as timed out. At the end of all tests there were 36 more tests with time outs. However, final report looks weird that reports 36 failed but should be 37:

2026-03-05T09:45:37.5050283Z Test Run Summary
2026-03-05T09:45:37.5050527Z   Overall result: Failed
2026-03-05T09:45:37.5058450Z   Test Count: 1416, Passed: 1362, **Failed: 36**, Warnings: 0, Inconclusive: 0, Skipped: 18
2026-03-05T09:45:37.5058984Z     Failed Tests - Failures: 0, Errors: 36, Invalid: 0
2026-03-05T09:45:37.5060054Z     Skipped Tests - Ignored: 18, Explicit: 0, Other: 0

Why they are not reported as Time out in summary while during test it is shown as:

2026-03-05T09:27:16.6117920Z Finishing test: BlahBlah.BlahTest("Blah","Stop","Blah/Stopping",null)
2026-03-05T09:27:16.6118254Z 	Result: TIMEOUT 0 asserts in 10.001101s
2026-03-05T09:27:16.6118474Z 	Details: Test exceeded Timeout value 10000ms.
2026-03-05T09:27:16.6118576Z 
2026-03-05T09:27:16.6118718Z 	Total tests: 880
2026-03-05T09:27:16.6118881Z 	Total SUCCESS tests: 878
2026-03-05T09:27:16.6119052Z 	Total ERROR tests: 1
2026-03-05T09:27:16.6119224Z 	**Total TIMEOUT tests: 1**

What happened to this test? and why summary does log as failed only but not as timed out count too?

To help the others diagnose and reproduce your issue, please include as many of the following as relevant:

• The full command line being used (we use opencover application to launch NUnit console):
  -Execute OpenCover.Console (File version 4.7.1221.0, Product version 4.7.1221.0-fae23d2): D:\TfsBuildAgent2020\_work\1022\s\.NuGet\packages\OpenCover\tools\OpenCover.Console.exe -target:"D:\TfsBuildAgent2020\_work\1022\s\.NuGet\packages\NUnit.ConsoleRunner\tools\nunit3-console.exe" -targetargs:""D:\TfsBuildAgent2020\_work\1022\s\bin\net48\Blah.AuditTrail.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net48\Blah.Blah.Interface.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net48\Blah.Blah.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net48\Blah.Blah.Interface.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net48\Blah.AgentStore.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net8.0\Blah.Agent.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net8.0\Blah.Blah.Interface.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net8.0\Blah.Blah.Interface.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net8.0\Blah.AgentStore.UnitTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net48\Blah.Blah.ComponentTests.dll" "D:\TfsBuildAgent2020\_work\1022\s\bin\net8.0-windows\Blah.Agent.ComponentTests.dll" --process:Multiple --labels=BeforeAndAfter --agents=1 --skipnontestassemblies --where="test=~^Blah.Agent.*" --result="D:\TfsBuildAgent2020\_work\1022\TestResults\results.xml";format=nunit2 --result="D:\TfsBuildAgent2020\_work\1022\TestResults\results_N3.xml";format=nunit3 --out="D:\TfsBuildAgent2020\_work\1022\TestResults\output.log"" -returntargetcode -targetdir:"D:\TfsBuildAgent2020\_work\1022\s\bin" -register:Path32 -register:Path64 -output:"D:\TfsBuildAgent2020\_work\1022\TestResults\coverage.xml" -filter:"+[Blah.Agent]* +[Blah.Agent.Interface]* +[Blah.Agent.Plugin]* +[Blah.AgentAuditTrail]* +[Blah.Blah]* +[Blah.Blah.Interface]* +[Blah.Blah.Interface]* +[Blah.AgentStore.Interface]*" -excludedirs:C:\Users\blah\AppData\Local\Temp\ -excludebyattribute:*.ExcludeFromCodeCoverage*;*.GeneratedCode* -communicationtimeout:60000
• Method of installation (e.g. NuGet, zip, msi): nuget package
• Log files (Run the console with --trace=Debug to produce these)
• Version of the NUnit Engine/Console : ```
  Executing: D:\TfsBuildAgent2020_work\1022\s.NuGet\packages\NUnit.ConsoleRunner\tools\nunit3-console.exe
  NUnit Console Runner 3.18.3 (Release)

- All versions of the NUnit Framework in use: console runner 3.18.3
- Whether the behaviour is any different when the tests are run using the --inprocess flag
Not yet tried this option

[TomasPeer]

I've applied filter to the smaller test scope and now I get 1 timeout and 2 test failures. Fallowing results recorded as fallows by DevOps build run:

Test Run Summary
  Overall result: Failed
  Test Count: 1416, Passed: 1396, Failed: 2, Warnings: 0, Inconclusive: 0, Skipped: 18
    Failed Tests - Failures: 1, Errors: 1, Invalid: 0
    Skipped Tests - Ignored: 18, Explicit: 0, Other: 0
  Start time: 2026-05-12 05:06:19Z
    End time: 2026-05-12 05:10:33Z
    Duration: 253.210 seconds

Since all results are uploaded to Elastic search now I can filter out for real test results:

As a result I get email notification with wrong count of failed tests: 2 but really total number of failed tests is 3.

Why overall summary is missing out the timed out test? Why two error tests listed as 1 failed and 1 error in detailed failed tests?