bUnit: Blame when running tests might hide bugs?

I have noticed that we get tests failing due to blame timeout, and that should actually only happen if a test deadlock and gets blocked, but it seems like if all tests actually run to the end.

The active test run was aborted. Reason: Test host process crashed
Data collector 'Blame' message: The specified inactivity time of 60 seconds has elapsed. Collecting hang dumps from testhost and its child processes.

But then, I also remember @linkdotnet mention that tests runs getting stuck when we removed it a little while back, so maybe there is something here to investigate.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 23 (9 by maintainers)

Most upvoted comments

Agreed.

egil on May 18, 2022

Kind of good/bad news: I removed almost every test and now bunit.web.tests starts to fail. Still only for >=.net6.0

linkdotnet on May 1, 2022

At least in verification we do not use the output of the previous step:

dotnet test ./tests/bunit.core.tests/bunit.core.tests.csproj -c release --logger:"console;verbosity=normal" --blame-hang --blame-hang-timeout 1m --blame-hang-dump-type none

When I reproduced locally I used exactly that line and also reproduced with the local github action. I am currently removing bunch of tests and run it again…like 10x each to see if I can boil it down…somehow.

linkdotnet on Apr 30, 2022

I removed GetAwaiter().GetResult() and also removed the DisposeComponents tests, but still the tests are failing.

I don’t want to set the hopes high but I removed TestRendererTest and on average I get way less failing tests.

linkdotnet on Apr 30, 2022