-
Notifications
You must be signed in to change notification settings - Fork 79
Usage of SpoonRunTask fails with ShellCommandUnresponsiveException #103
Comments
Timeout behaviour depends on what version of spoon runner you are using. The one that is probably in current plugin dependencies sets timeout to 0 if we do not specify any value explicitly. But if you replace it with a newer one, it should use a reasonable default value instead. As for |
It could be that the default value differs. Nevertheless when i use SpoonRunnerTask or the normal plugin with spoon block than the adbTimeout value shows different behaviour. spoon { This configuration and the task takeScreenshots(type: SpoonRunTask, dependsOn: ['assembleDebug', 'assembleAndroidTest']) { This configuration and the I think that shouldn't be a problem of the used spoon runner because both using the integrated spoon runner of the plugin, aren't they? EDIT: Points out that the spoon configuration takes seconds, the SpoonRunnerTask takes milliseconds. |
Task uses ms: Plugin extension uses seconds: On Wed, 6 Apr 2016 at 12:36 rzetzsche [email protected] wrote:
|
Thx, discover that seconds before your post. Maybe both should take the same time unit? |
I tried the usage of SpoonRunTask in my own task to generate screenshots and upload these to my webserver. But on execution i get an ShellCommandUnresponsiveException which i don't get when i execute the normal "gradlew spoon" command.
Additional to the issue, why is the testSize with SpoonRunTask not optional?
EDIT:
Ok same adbTimeout value of 3000 causes different behaviours. "gradlew spoon" executes without error, executing my own task causes "ShellCommandUnresponsiveException". If I increase the time in my own task it executes without issues too. Maybe they use different time units?
The text was updated successfully, but these errors were encountered: