-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hard to distinguish between a test host crash because of a hang or an actual crash #2593
Comments
I tried to tell to vstest.console that blame datacollector is killing the testhost, but I could not find a good way of wiring this together. This probably needs more love. |
In
|
@kartheekp-ms How does that relate to this issue? |
@ViktorHofer - The title of the issue says |
I think it would be best if VSTest itself logs all the information that is useful to identify a hanging test and not rely on an adapter's feature for that. |
This needs additional synchronization with datacollector. What happens is that as soon as we kill testhost the on exit event is triggered, but vstest.console does not know that there is something killing the testhost on purpose, so it just reports a crash, and then blame data collector sends a message saying it killed testhost. |
This is a new feature and won't be implemented, we are focusing on adding new features to Testing.Platform instead. https://aka.ms/testingplatform |
Example log:
The log says that the run was aborted because the test host process crashed but after that it says that the inactivity time has elapsed. I'm unsure if this means that the test process crashed because of a test crash or because a test hang.
AB#1583163
The text was updated successfully, but these errors were encountered: