stf
stf copied to clipboard
openstf
Over time of the using the STF local the `adb devices` failed with error: protocol fault (couldn't read status): Undefined error: 0
I use the STF version 3.2.0
What is the issue or idea you have?
Over time of the using the stf local I noticed that the adb devices returns error: protocol fault (couldn't read status): Undefined error: 0, but if to stop the stf - adb devices works correctly. After rebooting the machine I can use the STF and adb again without problems.
Does it only happen on a specific device? Please run adb devices -l and paste the corresponding row.
Please provide the steps to reproduce the issue.
The stf was started by the command /usr/local/bin/stf local --allow-remote --public-ip 192.168.0.214 --provider 192.168.0.214 --bind-dev-pub tcp://192.168.0.214:7114 --bind-dev-pull tcp://192.168.0.214:7116
What is the expected behavior?
Do you see errors or warnings in the stf local output? If so, please paste them or the full log here.
All devices status in the stf is disconnected.
Please run stf doctor and paste the output here.
2018-01-17T06:55:32.026Z INF/cli:doctor 798 [] OS Arch: x64
2018-01-17T06:55:32.028Z INF/cli:doctor 798 [] OS Platform: darwin
2018-01-17T06:55:32.029Z INF/cli:doctor 798 [] OS Platform: 16.7.0
2018-01-17T06:55:32.029Z INF/cli:doctor 798 [] Using Node 9.4.0
2018-01-17T06:55:32.053Z INF/cli:doctor 798 [] Using ZeroMQ 4.2.3
2018-01-17T06:55:32.073Z INF/cli:doctor 798 [] Using RethinkDB 2.3.6
2018-01-17T06:55:32.074Z INF/cli:doctor 798 [] Using GraphicsMagick 1.3.27
2018-01-17T06:55:32.078Z INF/cli:doctor 798 [] Using ADB 1.0.39
2018-01-17T06:55:32.083Z INF/cli:doctor 798 [*] Using ProtoBuf 3.5.1
Do not use macOS, adb is far from reliable on it. Use Linux if you want reliability.
On Wed, Jan 17, 2018 at 3:04 nIvanovp [email protected] wrote:
I use the STF version 3.2.0 What is the issue or idea you have? Over time of the using the stf local I noticed that the adb devices returns error: protocol fault (couldn't read status): Undefined error: 0, but if to stop the stf - adb devices works correctly. After rebooting the machine I can use the STF and adb again without problems. Does it only happen on a specific device? Please run adb devices -l and paste the corresponding row.
Please provide the steps to reproduce the issue. The stf was started by the command /usr/local/bin/stf local --allow-remote --public-ip 192.168.0.214 --provider 192.168.0.214 --bind-dev-pub tcp://192.168.0.214:7114 --bind-dev-pull tcp:// 192.168.0.214:7116 What is the expected behavior?
Do you see errors or warnings in the stf local output? If so, please paste them or the full log here. All devices status in the stf is disconnected. Please run stf doctor and paste the output here. 2018-01-17T06:55:32.026Z INF/cli:doctor 798 [ ] OS Arch: x64 2018-01-17T06:55:32.028Z INF/cli:doctor 798 [] OS Platform: darwin 2018-01-17T06:55:32.029Z INF/cli:doctor 798 [ ] OS Platform: 16.7.0 2018-01-17T06:55:32.029Z INF/cli:doctor 798 [] Using Node 9.4.0 2018-01-17T06:55:32.053Z INF/cli:doctor 798 [ ] Using ZeroMQ 4.2.3 2018-01-17T06:55:32.073Z INF/cli:doctor 798 [] Using RethinkDB 2.3.6 2018-01-17T06:55:32.074Z INF/cli:doctor 798 [ ] Using GraphicsMagick 1.3.27 2018-01-17T06:55:32.078Z INF/cli:doctor 798 [] Using ADB 1.0.39 2018-01-17T06:55:32.083Z INF/cli:doctor 798 [*] Using ProtoBuf 3.5.1
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/openstf/stf/issues/794, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB-_dIwdt8arqNxZ60OG8XL4gSyq2Q3ks5tLamTgaJpZM4Rg8gv .
