Completed
Last Updated: 15 Jul 2016 05:35 by Biswajit
ADMIN
Ivaylo
Created on: 12 Mar 2014 09:39
Type: Bug Report
4
"Can't reach the remote executor exception: Error while copying content to a stream" exception executing tests with a huge number of data iterations
When using scheduling to run tests remotely, when doubleclick on the result in the callendar it shows all test as passed, however the result is shown as failed and the message Can't reach the remote executor exception: Error while copying content to a stream. Refer to the screenshot attached. 

Screenshots and project files for repro provided in the internal description.
5 comments
Biswajit
Posted on: 15 Jul 2016 05:35
We found exactly the same error in Telerik test studio version 2016.2 while a coded step results in a lot of logs.
In addition to this the number of tests that is being reported is also wrong. If we run 12 tests some times we get 20 test results(more) stored in mongo DB and some times 4(less) . And these results are inconsistent.
We see there are 3 issues here. 
1. "Can't reach the remote executor exception: Error while copying content to a stream" exception when the logs of a coded step is more. Looks like telerik is not able to stream all the logs.
2. More number of test results being reported in the mongo DB.
3. Less number of test results being reported in mongo DB. We observed that telerik command line client does not wait for the execution to finish in all execution machines.

I wonder why Telerik has not fixed these issues till now.
John
Posted on: 16 Dec 2014 23:18
http://docs.telerik.com/teststudio/user-guide/knowledge-base/scheduling/increasestorageservicetimeout.aspx is a dead link.

I had this issue, then I deleted all local temp folders. Afterward it became the 'Can't reach the remote executor; exception: An error occurred while sending the request.'

I restarted the scheduling server (the host) and the 'stream' error returned. I'm using version 2014.4.1211.0
ADMIN
Daniel Djambov
Posted on: 21 Jul 2014 10:49
Telerik: with the implemented fixes, such issues are mostly avoided, at the same time we are reworking the backend communication between services and this issue will be obsolete in our upocomming releases.
ADMIN
Daniel Djambov
Posted on: 28 May 2014 10:39
Telerik: we have implemented 2 possible fixes for this problem, as we are unable to reproduce locally. The fixes are related to option to increase the SQL connection timeout (http://docs.telerik.com/teststudio/user-guide/knowledge-base/scheduling/increasestorageservicetimeout.aspx) and if a specific temp folder is not existing on a remote executor machine it throws inner exception, which marks the whole result as not finalized (failed after the timeout). The fixes are in our latest internal build from last week 2014.1.519 - please try it out to see if you can still face the issue.
David
Posted on: 06 May 2014 08:09
We are seeing this issue in build .428, it looks like it has been around for months now any news?