panda-jb-gcc47-tilt-stable-blob/#build=70 reboots when run cts on it

[Yongqin Liu]

When run cts on panda-jb-gcc47-tilt-stable-blob/#build=70, the android get rebooted.
the cts test commond is like this:

17:46:06 liuyq:cts$ ./android-cts/tools/cts-tradefed run cts --serial 0123456789ABCDEF --plan CTS |tee
Android CTS 4.1_r1
Non-interactive mode: Running initial command then exiting.
09-19 17:47:38 I/: Detected new device 0123456789ABCDEF
Using commandline arguments as starting command: [run, cts, --serial, 0123456789ABCDEF, --plan, CTS]
09-19 17:47:38 I/TestInvocation: Starting invocation for 'cts' on build '4.1_r1' on device 0123456789ABCDEF
09-19 17:47:38 I/0123456789ABCDEF: Created result dir 2012.09.19_17.47.38

17:49:26 liuyq:cts$

the cts package is https://dl.google.com/dl/android/cts/android-cts-4.1_r1-linux_x86-arm.zip

[Yongqin Liu (liuyq0307)]

log informatin on the console

[Yongqin Liu (liuyq0307)]

this problem also occurs on panda-jb-gcc47-tilt-stable-blob/#build=83

but with the original cts package https://dl.google.com/dl/android/cts/android-cts-4.0.3_r3-linux_x86-arm.zip,
there is no such reboot problem:(

[Yongqin Liu (liuyq0307)]

when run adb reboot, the output in logcat is similar to this,
so it's possible that the CTS has invoked the "adb reboot" during the test.

D/VoldCmdListener( 1344): volume unmount /mnt/sdcard force
D/Vold ( 1344): Volume sdcard state changing 4 (Mounted) -> 5 (Unmounting)
D/MountService( 1593): sendStorageIntent Intent { act=android.intent.action.MEDIA_EJECT dat=file:///mnt/sdcard (has extras) }
D/AndroidRuntime( 1680): Shutting down VM
W/dalvikvm( 1680): threadid=1: thread exiting with uncaught exception (group=0x41bb0300)
E/AndroidRuntime( 1680): FATAL EXCEPTION: main
E/AndroidRuntime( 1680): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.MEDIA_EJECT dat=file:///mnt/sdcard flg=0x10 (has extras) } in com.android.providers.media.MediaProvider$1@4219df40
E/AndroidRuntime( 1680): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:765)
E/AndroidRuntime( 1680): at android.os.Handler.handleCallback(Handler.java:615)
E/AndroidRuntime( 1680): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 1680): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1680): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 1680): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1680): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 1680): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 1680): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 1680): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1680): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 1680): at com.android.providers.media.MediaProvider$1.onReceive(MediaProvider.java:238)
E/AndroidRuntime( 1680): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:755)
E/AndroidRuntime( 1680): ... 9 more
I/Vold ( 1344): /mnt/secure/staging/.android_secure sucessfully unmounted
I/Vold ( 1344): /mnt/secure/asec sucessfully unmounted
I/Vold ( 1344): /mnt/secure/staging sucessfully unmounted
I/Vold ( 1344): /mnt/sdcard unmounted sucessfully
D/Vold ( 1344): Volume sdcard state changing 5 (Unmounting) -> 1 (Idle-Unmounted)
D/MountService( 1593): volume state changed for /mnt/sdcard (mounted -> unmounted)
D/MountService( 1593): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///mnt/sdcard (has extras) }

by the way, when run "adb shell reboot" the output of the logcat is different from this

[Yongqin Liu (liuyq0307)]

with the cts package I compiled locally from source, there is also no such reboot problem:(

[Yongqin Liu (liuyq0307)]

when set the log level to verbose, I got the following information,
it runs [fastboot, devices]:

cts-tf > run cts --serial 0123456789ABCDEF --plan CTS
09-29 10:25:35 D/TOKEN: Trying to tokenize the line 'run cts --serial 0123456789ABCDEF --plan CTS'
09-29 10:25:35 I/ConfigurationFactory: Loading configuration 'cts'
09-29 10:25:36 I/LargeOutputReceiver: Created tmp logcat file /tmp/logcat_0123456789ABCDEF_5551587310628695912.txt
09-29 10:25:36 I/DeviceManager: Allocated device 0123456789ABCDEF
09-29 10:25:36 D/BackgroundDeviceAction: Sleep for 5000 before starting logcat for 0123456789ABCDEF.
09-29 10:25:36 I/TestInvocation: Starting invocation for 'cts' on build '4.1_r1' on device 0123456789ABCDEF
09-29 10:25:36 I/0123456789ABCDEF: Created result dir 2012.09.29_10.25.36
09-29 10:25:41 D/BackgroundDeviceAction: Starting logcat for 0123456789ABCDEF.
09-29 10:26:28 I/0123456789ABCDEF: Collecting device info
09-29 10:26:36 D/RunnableResult: Running [fastboot, devices]
09-29 10:26:41 D/TestDevice: Device 0123456789ABCDEF state is now NOT_AVAILABLE
09-29 10:26:41 D/BackgroundDeviceAction: Sleep for 5000 before starting logcat for 0123456789ABCDEF.
09-29 10:26:46 D/BackgroundDeviceAction: Starting logcat for 0123456789ABCDEF.
09-29 10:26:46 D/BackgroundDeviceAction: com.android.ddmlib.AdbCommandRejectedException while running logcat on 0123456789ABCDEF. May see duplicated content in log.
09-29 10:26:51 I/DeviceStateMonitor: Waiting for device 0123456789ABCDEF to be ONLINE; it is currently NOT_AVAILABLE...
09-29 10:26:56 D/ManagedDeviceListener: Detected device connect 0123456789ABCDEF, id 194160712
09-29 10:26:56 D/ManagedDeviceListener: Updating IDevice for device 0123456789ABCDEF
09-29 10:26:56 D/TestDevice: Device 0123456789ABCDEF state is now OFFLINE
09-29 10:26:57 D/TestDevice: Device 0123456789ABCDEF state is now ONLINE
09-29 10:26:57 D/BackgroundDeviceAction: Sleep for 5000 before starting logcat for 0123456789ABCDEF.
09-29 10:27:02 D/BackgroundDeviceAction: Starting logcat for 0123456789ABCDEF.
cts-tf >

[Yongqin Liu (liuyq0307)]

From the 3 attached files above, we can see that the reboot is write in the source of the CTS package,
and the reboot will be run when there are more than 1 test packages in the plan.

So for us, we can have two options for this problem:
1. do the latest cts test via running all the packages listed in the CTS.xml one by one with "run cts --package" command
2. keep to use the older android-cts-4.0.3_r3-linux_x86-arm.zip we are using now until the new cts packages released.
   from the source, we can see that the reboot process does not exist

[Yongqin Liu (liuyq0307)]

another option:
3. use the CTS test package we build ourselves from source