Skip to content
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

[flakey test] The I/O operation has been aborted because of either a thread exit or an application request. #4670

Closed
Mpdreamz opened this issue Apr 23, 2020 · 0 comments
Labels

Comments

@Mpdreamz
Copy link
Member

Spotted an odd one on CI

System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
 ---> System.Net.Sockets.SocketException (995): The I/O operation has been aborted because of either a thread exit or an application request.

https://dev.azure.com/azure3/elasticsearch-net/_build/results?buildId=3722&view=logs&j=70d57b1a-3bb3-5656-1da8-d847c6de6c92&t=1327d875-a30a-5de5-c423-74b851577e38&l=1647

Seems to be related to:

dotnet/runtime#26629

RavenDB seemed to have similar issues and found it was related to Process inheriting handles. We have a similar situation where Elastic.Managed.Ephemeral boots Elasticsearch as child process.

We'll need to look adding this option to https://github.com/nullean/proc

[xUnit.net 00:12:31.8177855]     Tests.Document.Multiple.Bulk.BulkApiTests.ReturnsExpectedResponse [FAIL]
  X Tests.Document.Multiple.Bulk.BulkApiTests.ReturnsExpectedResponse [2m 19s]
  Error Message:
   Tests.Framework.EndpointTests.ResponseAssertionException : The operation was canceled.
Response Under Test:
Invalid NEST response built from a unsuccessful () low level call on POST: /nest-fluentasync-b81ec07a/_bulk?pretty=true&error_trace=true&pipeline=default-pipeline
# Invalid Bulk items:
# Audit trail of this API call:
 - [1] BadRequest: Node: http://localhost:9200/ Took: 00:01:00.2853572
 - [2] MaxTimeoutReached:
# OriginalException: System.Threading.Tasks.TaskCanceledException: The operation was canceled.
 ---> System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
 ---> System.Net.Sockets.SocketException (995): The I/O operation has been aborted because of either a thread exit or an application request.
   --- End of inner exception stack trace ---
   at void System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at int System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.GetResult(short token)
   at async Task<HttpResponseMessage> System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at async Task<HttpResponseMessage> System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
   at async Task<HttpResponseMessage> System.Net.Http.HttpConnectionPool.SendWithNtConnectionAuthAsync(HttpConnection connection, HttpRequestMessage request, bool doRequestAuth, CancellationToken cancellationToken)
   at async Task<HttpResponseMessage> System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, bool doRequestAuth, CancellationToken cancellationToken)
   at async Task<HttpResponseMessage> System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at async Task<HttpResponseMessage> System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task<HttpResponseMessage> sendTask, HttpRequestMessage request, CancellationTokenSource cts, bool disposeCts)
   at async Task<TResponse> Elasticsearch.Net.HttpConnection.RequestAsync<TResponse>(RequestData requestData, CancellationToken cancellationToken) in D:/a/1/s/src/Elasticsearch.Net/Connection/HttpConnection.cs:line 153
# Request:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants