[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb

[oldel...@java.net (JIRA)]

Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I've had a quick look over the Wireshark captures. In the "bad" capture the emulator never responds to the connection (CNXN) request from ADB and at first glance that seems to jam the whole adb<->emulator connection up. I haven't worked out whether ADB or the emulator is a fault because ADB only gives the emulator about 0.5 second to respond before it forcefully closes the connection. The emulator doesn't release (TCP FIN) its end of the connection for about another 17 seconds. For reference this all occurs in the TCP connection from port 62625 to port 5752 that starts at packet 371 in the bad pcap file. Good connection looks like 00000000 43 4e 58 4e 00 00 00 01 00 10 00 00 07 00 00 00 CNXN.... ........ 00000010 32 02 00 00 bc b1 a7 b1 68 6f 73 74 3a 3a 00 2....... host::. 00000000 43 4e 58 4e 00 00 00 01 00 10 00 00 5a 00 00 00 CNXN.... ....Z... 00000010 41 22 00 00 bc b1 a7 b1 64 65 76 69 63 65 3a 3a A"...... device:: 00000020 72 6f 2e 70 72 6f 64 75 63 74 2e 6e 61 6d 65 3d ro.produ ct.name= 00000030 67 6f 6f 67 6c 65 5f 73 64 6b 3b 72 6f 2e 70 72 google_s dk;ro.pr 00000040 6f 64 75 63 74 2e 6d 6f 64 65 6c 3d 67 6f 6f 67 oduct.mo del=goog 00000050 6c 65 5f 73 64 6b 3b 72 6f 2e 70 72 6f 64 75 63 le_sdk;r o.produc 00000060 74 2e 64 65 76 69 63 65 3d 67 65 6e 65 72 69 63 t.device =generic 00000070 3b 00 ;. 0000001F 4f 50 45 4e 17 00 00 00 00 00 00 00 1f 00 00 00 OPEN.... ........ 0000002F ed 0b 00 00 b0 af ba b1 73 68 65 6c 6c 3a 67 65 ........ shell:ge 0000003F 74 70 72 6f 70 20 64 65 76 2e 62 6f 6f 74 63 6f tprop de v.bootco 0000004F 6d 70 6c 65 74 65 00 mplete. 00000072 4f 4b 41 59 01 00 00 00 17 00 00 00 00 00 00 00 OKAY.... ........ 00000082 00 00 00 00 b0 b4 be a6 ........ 0000008A 57 52 54 45 01 00 00 00 17 00 00 00 02 00 00 00 WRTE.... ........ 0000009A 17 00 00 00 a8 ad ab ba 0d 0a ........ .. 00000056 4f 4b 41 59 17 00 00 00 01 00 00 00 00 00 00 00 OKAY.... ........ 00000066 00 00 00 00 b0 b4 be a6 ........ 000000A4 43 4c 53 45 00 00 00 00 17 00 00 00 00 00 00 00 CLSE.... ........ 000000B4 00 00 00 00 bc b3 ac ba ........ 0000006E 43 4c 53 45 17 00 00 00 01 00 00 00 00 00 00 00 CLSE.... ........ 0000007E 00 00 00 00 bc b3 ac ba ........ ... truncated here because it is uninteresting for our purposes... Bad connection stream contains 00000000 43 4e 58 4e 00 00 00 01 00 10 00 00 07 00 00 00 CNXN.... ........ 00000010 32 02 00 00 bc b1 a7 b1 68 6f 73 74 3a 3a 00 2....... host::. I likely will not get to look at this further for at least the next 36 hours. I will do a bit of digging in the emulator/ADB code to see if my analysis matches what the code does once I get some spare time.

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.