|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Tobias can you post a "good" log too. That would be helpful for myself/others to make sense of the various warnings/errors in the log that are just "normal".
That said around like 2834 of your log the following exists
D/AlertReceiver( 1323): onReceive: a=android.intent.action.BOOT_COMPLETED Intent { act=android.intent.action.BOOT_COMPLETED flg=0x8000010 cmp=com.android.calendar/.alerts.AlertReceiver (has extras) } I/ActivityManager( 384): Delay finish: com.android.calendar/.alerts.AlertReceiver D/AlertUtils( 1323): Flushing old alerts from shared prefs table D/AlertService( 1323): 0 Action = ""This suggests to me that the emulator thinks that boot has completed but that it is not connected to ADB properly. That would add some weight to the theory that something is going wrong in the early emulator<->ADB communications.