|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You could try downgrading to plugin version 2.10 and see whether it makes a difference.
But the strange part in your most recent log is that you get "device offline" a lot — which is normal, as we're waiting for the emulator to start. But then it switches to "device not found", which indicates that the ADB server has somehow forgotten about the emulator.
This could happen either because the ADB server crashed, and was then automatically restarted upon the next "adb shell" command (though this won't be visible in the logs as we don't log stdout in this case), or because the emulator itself has crashed.
For the other cases, where the emulator remains connected to ADB, but remains in the "offline" state (i.e. the original reason for this bug report), since I can't reproduce this, it's hard to say what the fix should be.
Killing and restarting the ADB server doesn't help, as we (currently) use ports above the usual 5554-5590![]()
range, so the existing emulator won't be auto-detected by the new ADB server instance.
Since we're no longer using "localhost:12345", we can't use the "adb connect" command either to re-introduce the emulator to ADB.
However, we can send the ADB protocol command directly to the server to do the same, e.g.
echo '0012host:emulator:5800' | nc localhost 9876
Where 5800 is the emulator's ADB port, and 9876 is the ADB server port.
But again, without being able to reproduce this, it's hard to tell whether this will be helpful. Unless anybody has any other ideas, I can try and create a patch including better logging (to detect adb crashes), and possibly manually reconnecting to the device in place of the now-redundant "adb connect" code.