-
Notifications
You must be signed in to change notification settings - Fork 292
Open
Labels
Area: MTPBelongs to the Microsoft.Testing.Platform core libraryBelongs to the Microsoft.Testing.Platform core library
Description
Summary
I'm experiencing some deadlock bugs in some code, and these crop up in tests. I set a timeout flag of 10 minutes so that tests don't sit there indefinitely hanging. And I see output like this when it aborts:
[+180/x0/?0] Dekaf.Tests.Integration.dll (net10.0|x64) - 2 tests running (9m 59s)
[+180/x0/?0] Dekaf.Tests.Integration.dll (net10.0|x64) - 2 tests running (10m 00s)
The test run was cancelled.
[+180/x0/?0] Dekaf.Tests.Integration.dll (net10.0|x64) - 2 tests running (10m 00s)
Test run summary: Aborted - /home/runner/work/Dekaf/Dekaf/tests/Dekaf.Tests.Integration/bin/Release/net10.0/Dekaf.Tests.Integration.dll (net10.0|x64)
total: 180
failed: 0
succeeded: 180
skipped: 0
duration: 10m 00s 228ms
As you can see, there seems to be 2 tests that are hanging, but I never find out which ones.
Proposed Feature
When a test run is cancelled/aborted, can we print which tests were in-progress when it cancelled? For scenarios where there may be extremely slow tests, or deadlocks, this helps us narrow down which tests/the code they are testing are problematic.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: MTPBelongs to the Microsoft.Testing.Platform core libraryBelongs to the Microsoft.Testing.Platform core library