Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I managed to reproduce the issue by crashing the agent with a stack overflow in a test.
This fix wraps all of the remoting calls in ProcessRunner in a try/catch. If it crashes running or exploring tests, it returns a
TestEngineResult
that contains the remoting exception. The full results are now properly displayed. As a side effect, I noticed that while testing this issue, nunit-agents were left running in the background. This is no longer happening, I assume because we are now stopping the agents that are still running.My only concern with this is the fake test results where I fake data I don't know. I checked the final TestResult.xml and it looks fine.
My now successfully reported crash run is below. Before, it ended with an exception and no results were displayed.
The TestResult.xml is