Get stuck on "Watching emulator stdOut for boot completion..." in RobotiumRC

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Instruments the SAFSTCPMessenger and RobotiumTestRunner projects.(ant or 
eclipse)
2. Intall my project and SAFSTCPMessenger and RobotiumTestRunner projects  (adb 
install)
3. Run the test class on testNG or jUnit4.
4. Get stuck after opening emulator and "Watching emulator stdOut for boot 
completion".

What is the expected output? What do you see instead?
Expected to start launch app and run tests.

What version of the product are you using? On what operating system?
- Win 7 32bits
- Robotium RC 2012.12.12

Please provide any additional information below.

- Console log on run test:
SoloTest INFO: Detected 0 device/emulators attached.
SoloTest INFO: Attempting to launch EMULATOR_AVD: test
Bypassing ServerSocket Socket Thread...
Watching emulator stdOut for boot completion...
HAX is working and emulator runs in fast virt mode

it can work well if i keep emulator open first.

Original issue reported on code.google.com by enduranc...@gmail.com on 1 Aug 2013 at 9:23

[GoogleCodeExporter]

There is a known issue with some versions of emulator output monitoring with 
that older release of RobotiumRC.

If you can, please try the latest release of RobotiumRC at

http://sourceforge.net/projects/safsdev/files

If the problem persists, we would enjoy a logcat output of the emulator startup 
so we can enhance the detection support.

Carl Nagle
SAS Institute, Inc.
Planning, Operations and Strategy
General Applications and Tools
Carl.Nagle@sas.com

Original comment by carl.na...@sas.com on 2 Aug 2013 at 3:29

• Changed state: Started

[GoogleCodeExporter]

I tried the latest release - RobotiumRC 2013.07.12 on two different android 
versions, 4.1.2 and 2.3.3, both use Intel Atom(x86) CPU.
This problem still exists.

Please see attachment to get the logcat output.

Thanks.

Original comment by enduranc...@gmail.com on 2 Aug 2013 at 6:33

Attachments:

• log_4.1.2.txt
• log_2.3.3.txt

[GoogleCodeExporter]

Thank you for these logs.

Please find attached a replacement safsautoandroid.jar that, hopefully, might 
resolve the issue for many more scenarios--maybe all.

I've also added a default timeout of 5 minutes (instead of infinite) for boot 
completion detection.  Testers can optionally change this timeout with a new 
static value in the StartEmulator class:

See 
http://safsdev.sourceforge.net/doc/org/safs/android/auto/lib/StartEmulator.html#
setBootCompletionTimeout%28long%29

Carl Nagle
SAS Institute, Inc.
SAS Research & Development
Planning, Operations and Strategy
General Applications and Tools
carl.nagle@sas.com

Original comment by carl.na...@sas.com on 2 Aug 2013 at 5:13

• Changed state: Accepted

Attachments:

• safsautoandroid.jar

[GoogleCodeExporter]

I tried your new safsautoandroid.jar, this issue still exists....
I invoke preparation() method which belongs to SoloTest to do this open 
emulator job.

Please see attachment to get new Logcat output.

Original comment by enduranc...@gmail.com on 5 Aug 2013 at 6:36

Attachments:

• log_4.1.2.txt
• log_2.3.3.txt

[GoogleCodeExporter]

I have been able to duplicate the failure in my own Atom x86 emulator.  This is 
the same or similar issue that Dietrich Schulten put forth in previous 
discussions/issues.  That is, the emulator stops sending output into it's 
stdOut so attempts to read stdout block.

I am currently working to resolve the issue and hope to have a new JAR for 
others to try shortly.

Carl Nagle
SAS Institute, Inc.
Research & Development
Planning, Operations and Strategy
General Applications and Tools
Carl.Nagle@sas.com

Original comment by carl.na...@sas.com on 5 Aug 2013 at 6:36

[GoogleCodeExporter]

I think I have the best candidate fix in this attachment.

Since monitoring the emulator stdOut was too problematic, I've refactored to 
monitor the Android window service initializing the Launcher Activity window.

Please take it and give it a try.  If you will, I'd like to see your console 
output and logs--even if this is all successful.

Carl Nagle
SAS Institute, Inc.
Research & Development
Planning, Operations and Strategy
General Applications and Tools
Carl.Nagle@sas.com

Original comment by carl.na...@sas.com on 6 Aug 2013 at 9:18

• Changed state: Fixed

Attachments:

• safsautoandroid.jar

[GoogleCodeExporter]

It do works now, but it can't terminate emulator automaticlly..

console output:
performRemoteShutdown ignoring TimeoutException: waitForRemoteShutdown Timeout 
before Shutdown
SoloTest INFO:  checking for launched emulators...
DUtilities attempting ProcessMonitor shutdownProcess...
SoloTest WARN: We fail to stop the emulator launched by us.
Emulator(s) shutdown? false
SoloTest DEBUG: terminate successfully.

do you have any idea about this?

BTW, do you provide any method to uninstall application ?

See attachment to get latest log and console output..

thanks

Original comment by enduranc...@gmail.com on 7 Aug 2013 at 3:11

Attachments:

• console_output_4.1.2.txt
• log_4.1.2.txt

[GoogleCodeExporter]

Unfortunately, the site tells me that "Issue attachment storage quota 
exceeded".  So I cannot provide you an updated safsautoandroid.jar which fixes 
the shutdown problem.

I noticed the shutdown problem while debugging the boot completion problem.  
But fixed it AFTER delivering the boot completion fix.  I will attempt to 
provide a RobotiumRC Overlay on the SourceForge SAFSDEV site (Home of 
RobotiumRC) within the next few days.  You can also email me directly and I 
will try to get you the jar.

For uninstalling an APK and other nifty tools, look at just some of the APIs 
that come with SAFS AutoAndroid delivered with RobotiumRC:

http://safsdev.sourceforge.net/doc/org/safs/android/auto/lib/package-frame.html

http://safsdev.sourceforge.net/doc/org/safs/android/auto/lib/DUtilities.html#uni
nstallAPKPackage%28java.lang.String,%20boolean%29

Carl Nagle
SAS Institute, Inc.
Research & Development
Planning, Operations and Strategy
General Applications and Tools
Carl.Nagle@sas.com

Original comment by carl.na...@sas.com on 7 Aug 2013 at 1:59

[GoogleCodeExporter]

It can be terminate successful. awesome.
Thanks a lot.

Original comment by enduranc...@gmail.com on 9 Aug 2013 at 2:04

[GoogleCodeExporter]

Thanks Carl for the fix. Even I was facing the same issue 'Watching emulator 
stdOut for boot completion..'. Used the attached jar(posted in this 
discussion)and I'm able to launch and terminate the emulator successfully. Hope 
this fix would be a part of upcoming releases of RC.

-Kiran

Original comment by contactk...@gmail.com on 18 Aug 2013 at 9:07