Exception: runningEmulators: retrying java.lang.IllegalStateException: Process [script, -F, ..., adb, devices] exited with non-zero code 1 #84
Comments
ziem
changed the title
|
Hm, which version of adb/Android SDK tools are you using?
…On Mon, Jul 10, 2017, 02:48 Ziem ***@***.***> wrote:
Hi,
I decided to give composer a shot and unfortunately, I can't make it work.
After executing:
java -jar composer-0.2.3.jar --apk app/build/outputs/apk/app.apk --test-apk app/build/outputs/apk/app-androidTest.apk --test-package package --test-runner package.MultiDexAndroidJUnitRunner
I receive following errors:
[Mon Jul 10 09:14:25 CEST 2017]: runningEmulators: retrying
java.lang.IllegalStateException: Process [script, -F,
/.../2920001465450.output, /usr/local/share/android-sdk/platform-tools/adb,
devices] exited with non-zero code 1 .
[Mon Jul 10 09:14:25 CEST 2017]: runningEmulators: retrying
java.lang.IllegalStateException: Process [script, -F,
/.../2917665125786.output, /usr/local/share/android-sdk/platform-tools/adb,
devices] exited with non-zero code 1 .
[Mon Jul 10 09:14:25 CEST 2017]: runningEmulators: retrying
java.lang.IllegalStateException: Process [script, -F,
/...2919879561453.output, /usr/local/share/android-sdk/platform-tools/adb,
devices] exited with non-zero code 1 .
[Mon Jul 10 09:14:25 CEST 2017]: runningEmulators: retrying
java.lang.IllegalStateException: Process [script, -F,
/.../2919212779445.output, /usr/local/share/android-sdk/platform-tools/adb,
devices] exited with non-zero code 1 .
[Mon Jul 10 09:14:25 CEST 2017]: Error during getting connectedAdbDevices,
error = java.lang.IllegalStateException: Process [script, -F,
/.../2917033128684.output, /usr/local/share/android-sdk/platform-tools/adb,
devices] exited with non-zero code 1
Exception in thread "main" java.lang.IllegalStateException: Process
[script, -F, /.../2917033128684.output,
/usr/local/share/android-sdk/platform-tools/adb, devices] exited with
non-zero code 1
at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt:97)
at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt)
at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:72)
at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:32)
at rx.Observable.unsafeSubscribe(Observable.java:10256)
at
rx.internal.operators.OperatorSubscribeOn$SubscribeOnSubscriber.call(OperatorSubscribeOn.java:100)
at
rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:230)
at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
To make sure that adb works fine, just before running composer, I executed:
adb devices
which printed:
List of devices attached
emulator-5554 device
010a625c2eaab236 device
echo $ANDROID_HOME
/usr/local/share/android-sdk
What am I doing wrong? How to fix it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#84>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3EBveJg2ox0RXmr2kP4dtrVaBG6Lks5sMfN9gaJpZM4OSmvw>
.
|
|
I'm using Android Debug Bridge version 1.0.39 (Revision 3db08f2c6889-android) and Android SDK Tools version 26.0.2. |
|
Can you please try Thanks! |
|
Yup:
|
|
Hmm, so it returns successful result code, can you try to launch Composer again please? Maybe the error is gone now, sometimes (pretty rare though adb server needs to be restarted) |
|
I added
to the jenkins job just before:
but unfortunately error is still present.
|
|
Ah, so you're running Composer on macOS… In general it works on macOS, but looks like we're facing some corner case. To debug it further we need to see output of adb invocation, Composer (and Swarmer) interacts with external tools like You can try to catch them and send us back but that would be tricky since they're deleted on exit… Or you can wait until we add an option to keep those files #91, but it'll take some time because. |
|
Yes, I'm running it on macOS - I should've added it to my initial post. I will try to somehow copy them. Thanks for your help. |
Hi,
I decided to give composer a shot and unfortunately, I can't make it work.
After executing:
I receive following errors:
To make sure that adb works fine, just before running composer, I executed:
which printed:
What am I doing wrong? How to fix it?
The text was updated successfully, but these errors were encountered: