Comment 12 for bug 1006234

CTS and MONKEY test fails on build #350

Android-build : https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc46-igloo-stable-blob/#build=350
Job id : http://validation.linaro.org/lava-server/scheduler/job/24164
log file : http://validation.linaro.org/lava-server/scheduler/job/24164/log_file

cts test:

From logs:
---------
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: android.core.tests.libcore.package.org package complete: Passed 0, Failed 0, Not Executed 1907
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: Test package android.core.tests.libcore.package.sun started
LAVA: (stdout) 07-0WARNING: Could not read cpu information
WARNING: Could not read board information
WARNING: Could not read memory information
ERROR: Test execution error: The result (cts1341320569.0) is not existed.
3 13:28:15 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: android.core.tests.libcore.package.sun package complete: Passed 0, Failed 0, Not Executed 2
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: Test package android.core.tests.libcore.package.tests started
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: android.core.tests.libcore.package.tests package complete: Passed 0, Failed 0, Not Executed 2643
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: Test package android.core.vm-tests-tf started
LAVA: (stdout) 07-03 13:28:15 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:16 I/192.168.1.243:5555: android.core.vm-tests-tf package complete: Passed 0, Failed 0, Not Executed 3098
LAVA: (stdout) 07-03 13:28:16 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:16 I/192.168.1.243:5555: Test package android.tests.appsecurity started
LAVA: (stdout) 07-03 13:28:16 I/192.168.1.243:5555: -----------------------------------------
LAVA: (stdout) 07-03 13:28:18 I/192.168.1.243:5555: Saved log device_logcat_7706288674799225125.zip
LAVA: (stdout) 07-03 13:28:18 I/192.168.1.243:5555: Saved log host_log_2059514123584845667.zip
LAVA: (stdout) 07-03 13:28:18 I/192.168.1.243:5555: android.tests.appsecurity package complete: Passed 0, Failed 0, Not Executed 6
LAVA: (stdout) 07-03 13:28:18 I/192.168.1.243:5555: Created xml report file at file:///tmp/lava-android-test/tmpbOb6eE/./android-cts/tools/../../android-cts/repository/results/2012.07.03_13.06.45/testResult.xml
LAVA: (stdout) 07-03 13:28:19 I/192.168.1.243:5555: XML test result file generated at 2012.07.03_13.06.45. Passed 1, Failed 0, Not Executed 17150
LAVA: (stdout) 07-03 13:28:19 I/192.168.1.243:5555: Time: 21m 33s
LAVA: (stdout) 07-03 13:28:23 W/DeviceManager: Freed device 192.168.1.243:5555 is unavailable. Removing from use.
LAVA: (stdout) 07-03 13:28:23 I/CommandScheduler: All done
LAVA: (stdout) Saved log to /tmp/tradefed_global_log_274889395310878022.txt
LAVA: (stdout) 07-03 13:30:27 E/BackgroundDeviceAction: Device 192.168.1.243:5555 not online
ANDROID TEST RUN COMPLETE: Result id is 'cts1341320569.0'

<LAVA_DISPATCHER>2012-07-03 01:30:27 PM INFO: Execute adb command on host: adb disconnect 192.168.1.243

No such device 192.168.1.243:5555

<LAVA_DISPATCHER>2012-07-03 01:30:27 PM WARNING: [ACTION-E] lava_android_test_run is finished with error (Failed to run test case(cts) on device(192.168.1.243:5555) with return value: 1).

Comments:
----------
Looks like there is issue with device under test as I see logs like
WARNING: Could not read cpu information
WARNING: Could not read board information
WARNING: Could not read memory information
...
ERROR: Test execution error: The result (cts1341320569.0) is not existed.

Monkey test:

From logs:
---------
<LAVA_DISPATCHER>2012-07-03 01:30:27 PM INFO: [ACTION-B] lava_android_test_run is started with {'timeout': 18000, u'test_name': u'monkey'}
---------
Comments:
Monkey test does not complete and the device gets rebooted again.
The issue may be that board is not responding and device is forced to reboot and then the monkey test never gets scheduled after that.