Option to ignore any device that failed to run all the tests.

yogurtearl commented 10 years ago

Similar to #191 , sometimes adb has a hickup that causes it to not be get the results from one of the devices.

It would be nice to have an option to ignore these failures.

Test failed to run to completion. Reason: 'Test run failed to complete. Expected 72 tests, received 46'. Check device logcat for details

carlospaulino commented 10 years ago

I second @yogurtearl request

tomrozb commented 10 years ago

++

screw-spike commented 8 years ago

I have the same ,but sometimes it's OK! Test failed to run to completion. Reason: 'Test run failed to complete. Expected 20 tests, received 14'. Check device logcat for details Tests on ASTEROID - 4.3 failed: Test run failed to complete. Expected 20 tests, received 14

Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:connectedDebugAndroidTest'. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46) at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)

kirillzh commented 8 years ago

Having the same problem, was it resolved?

omelkova commented 6 years ago

@JakeWharton I faced the same problem with latest spoon version. Is there any understanding what can cause this error? I can send additional info about the test run if it may help to investigate Thank you very much for this useful library!

JD-90 commented 6 years ago

@omelkova Hey, have you been able to identify this issue's root cause? It's failing most of my tests runs for no apparent reason.

raviranjanchaudhari-tudip commented 5 years ago

I faced the same problem with the latest build version. Is there any understanding of what can cause this error?

raviranjanchaudhari-tudip commented 5 years ago

Does anyone have a solution on the same?

square / spoon

Option to ignore any device that failed to run all the tests. #192