INSTRUMENTATION_RESULT: shortMsg=Process crashed.

[mayank]

Hi,

Can someone please explain the reason for an error like:-

INSTRUMENTATION_RESULT: shortMsg=Process crashed.
INSTRUMENTATION_CODE: 0

Coz I have seen the same target/test code combination work in most
cases, however in some odd cases I end up seeing this error. What
could explain this inconsistent behaviour?

Regards

[Erik Hansen]

Its because the application you are testing crashed.
Looking for stack traces in logcat will often provide cluses as to why
that happened.


/erik

[marekdef]

Isn't it you are starting another round of test before the old one
finished.
Anyway in logcat there should be an answer.

[naveed]

I've faced this issue not sure the same is the case with you. Can you please come up with more info like, 

you are executing on emulator/device?

what are the specs of devices ? 

etc...

On Wednesday, May 22, 2013 12:12:10 AM UTC+5, Franck Derunes wrote:

I also get this error for 20% of my tests

here is the bat dos command part

start /B /WAIT adb  -s %DEVICESERIAL% shell am force-stop com.myapp.test

start /B /WAIT adb  -s %DEVICESERIAL% shell am force-stop com.myapp

start /B /WAIT adb -s %DEVICESERIAL% shell rm -r mnt/sdcard/Robotium-Screenshots

start /B /WAIT adb -s %DEVICESERIAL% shell mkdir mnt/sdcard/Robotium-Screenshots

start /B /WAIT adb -s %DEVICESERIAL% uninstall com.myapp

start /B /WAIT adb -s %DEVICESERIAL% uninstall %TESTNAME%

start /B /WAIT adb -s %DEVICESERIAL% shell rm -r mnt/sdcard/myapp

start /B /WAIT adb -s %DEVICESERIAL% install -r %APPPATHFILENAME%

start /B /WAIT adb -s %DEVICESERIAL% install %TESTPATHFILENAME%

start /B /WAIT adb  -s %DEVICESERIAL% shell pm clear com.myapp

echo test starting...

start /B /WAIT adb -s %DEVICESERIAL% logcat -c

IF NOT %ERRORLEVEL%==0 goto :error

start /B /WAIT adb -s %DEVICESERIAL% shell am instrument -w ^%TESTNAME%/android.test.InstrumentationTestRunner || goto :error

IF NOT %ERRORLEVEL%==0 goto :error

there is nothing in the logcat that could explain

[Sunil Alapati]

i guess you're application got crashed in that cases. try to execute those odd cases manually and see if it crashes.

On Wed, May 22, 2013 at 12:42 AM, Franck Derunes <fder...@gmail.com> wrote:

I also get this error for 20% of my tests

here is the bat dos command part

start /B /WAIT adb  -s %DEVICESERIAL% shell am force-stop com.myapp.test

start /B /WAIT adb  -s %DEVICESERIAL% shell am force-stop com.myapp

start /B /WAIT adb -s %DEVICESERIAL% shell rm -r mnt/sdcard/Robotium-Screenshots

start /B /WAIT adb -s %DEVICESERIAL% shell mkdir mnt/sdcard/Robotium-Screenshots

start /B /WAIT adb -s %DEVICESERIAL% uninstall com.myapp

start /B /WAIT adb -s %DEVICESERIAL% uninstall %TESTNAME%

start /B /WAIT adb -s %DEVICESERIAL% shell rm -r mnt/sdcard/myapp

start /B /WAIT adb -s %DEVICESERIAL% install -r %APPPATHFILENAME%

start /B /WAIT adb -s %DEVICESERIAL% install %TESTPATHFILENAME%

start /B /WAIT adb  -s %DEVICESERIAL% shell pm clear com.myapp

echo test starting...

start /B /WAIT adb -s %DEVICESERIAL% logcat -c

IF NOT %ERRORLEVEL%==0 goto :error

start /B /WAIT adb -s %DEVICESERIAL% shell am instrument -w ^%TESTNAME%/android.test.InstrumentationTestRunner || goto :error

IF NOT %ERRORLEVEL%==0 goto :error

there is nothing in the logcat that could explain

On Friday, March 25, 2011 7:55:37 AM UTC-7, mayank wrote:

--
You received this message because you are subscribed to the Google Groups "Robotium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotium-develo...@googlegroups.com.
To post to this group, send email to robotium-...@googlegroups.com.
Visit this group at http://groups.google.com/group/robotium-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.