-
Notifications
You must be signed in to change notification settings - Fork 341
Don't print socket transport error in console #4493
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
Don't print socket transport error in console #4493
Conversation
| remoteEndPoint, | ||
| localEndPoint); | ||
| error = ioException; | ||
| // Do not pass the error to the caller, the transport was torn down because testhost |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not super happy about this, but if we do it later in the code we end up ignoring errors for all types of transports (we have just 1 type now, but the abstractions are there). Or we have to match a specific type of error, and then make sure it was raised here, which is pretty much the same as not raising it at all.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Description
Avoid forwarding stack error when testhost disconnects unexpectedly. This error steals developer focus from the other more important error, which is either the testhost error message, or simply "testhost crashed" without any additional info.
Related issue
Fix #4461
Kindly link any related issues. E.g. Fixes #xyz.