@Yongqin, Yes, that screen capture is possibly the root cause behind. Vishal, Naresh and I are discussing this issue in email thread and a test job definition has been created by Vishal based on every individual package rather than plan:
https://validation.linaro.org/scheduler/job/127259/definition
I just tried the second package in your test definition, it can be launched and run well:
cts-tf > run cts --package android.acceleration 05-19 17:35:05 I/TestInvocation: Starting invocation for 'cts' on build '4.4_r1' on device 192.168.1.70:5555 05-19 17:35:05 I/192.168.1.70:5555: Created result dir 2014.05.19_17.35.05 05-19 17:35:22 I/192.168.1.70:5555: Collecting device info 05-19 17:35:24 I/192.168.1.70:5555: ----------------------------------------- 05-19 17:35:24 I/192.168.1.70:5555: Test package android.acceleration started 05-19 17:35:24 I/192.168.1.70:5555: ----------------------------------------- 05-19 17:35:30 I/192.168.1.70:5555: android.acceleration.cts.HardwareAccelerationTest#testIsHardwareAccelerated PASS 05-19 17:35:32 I/192.168.1.70:5555: android.acceleration.cts.HardwareAccelerationTest#testNotAttachedView PASS 05-19 17:35:34 I/192.168.1.70:5555: android.acceleration.cts.SoftwareAccelerationTest#testIsHardwareAccelerated PASS 05-19 17:35:37 I/192.168.1.70:5555: android.acceleration.cts.SoftwareAccelerationTest#testNotAttachedView PASS 05-19 17:35:38 I/192.168.1.70:5555: android.acceleration.cts.WindowFlagHardwareAccelerationTest#testIsHardwareAccelerated PASS 05-19 17:35:41 I/192.168.1.70:5555: android.acceleration.cts.WindowFlagHardwareAccelerationTest#testNotAttachedView PASS 05-19 17:35:46 I/192.168.1.70:5555: Saved log device_logcat_5110948498854286530.zip 05-19 17:35:46 I/192.168.1.70:5555: Saved log host_log_5670204231979926187.zip 05-19 17:35:46 I/192.168.1.70:5555: android.acceleration package complete: Passed 6, Failed 0, Not Executed 0 05-19 17:35:46 I/192.168.1.70:5555: Created xml report file at file:///home/noname/work/linaro/linaro-armv8/android-cts/tools/./../../android-cts/repository/results/2014.05.19_17.35.05/testResult.xml 05-19 17:35:46 I/192.168.1.70:5555: XML test result file generated at 2014.05.19_17.35.05. Passed 6, Failed 0, Not Executed 0 05-19 17:35:46 I/192.168.1.70:5555: Time: 40s cts-tf >
@Yongqin, Yes, that screen capture is possibly the root cause behind. Vishal, Naresh and I are discussing this issue in email thread and a test job definition has been created by Vishal based on every individual package rather than plan:
https:/ /validation. linaro. org/scheduler/ job/127259/ definition
I just tried the second package in your test definition, it can be launched and run well:
cts-tf > run cts --package android. acceleration 1.70:5555: Created result dir 2014.05.19_17.35.05 1.70:5555: Collecting device info 1.70:5555: ------- ------- ------- ------- ------- ------ 1.70:5555: Test package android. acceleration started 1.70:5555: ------- ------- ------- ------- ------- ------ 1.70:5555: android. acceleration. cts.HardwareAcc elerationTest# testIsHardwareA ccelerated PASS 1.70:5555: android. acceleration. cts.HardwareAcc elerationTest# testNotAttached View PASS 1.70:5555: android. acceleration. cts.SoftwareAcc elerationTest# testIsHardwareA ccelerated PASS 1.70:5555: android. acceleration. cts.SoftwareAcc elerationTest# testNotAttached View PASS 1.70:5555: android. acceleration. cts.WindowFlagH ardwareAccelera tionTest# testIsHardwareA ccelerated PASS 1.70:5555: android. acceleration. cts.WindowFlagH ardwareAccelera tionTest# testNotAttached View PASS 1.70:5555: Saved log device_ logcat_ 511094849885428 6530.zip 1.70:5555: Saved log host_log_ 567020423197992 6187.zip 1.70:5555: android. acceleration package complete: Passed 6, Failed 0, Not Executed 0 1.70:5555: Created xml report file at file:// /home/noname/ work/linaro/ linaro- armv8/android- cts/tools/ ./../.. /android- cts/repository/ results/ 2014.05. 19_17.35. 05/testResult. xml 1.70:5555: XML test result file generated at 2014.05. 19_17.35. 05. Passed 6, Failed 0, Not Executed 0 1.70:5555: Time: 40s
05-19 17:35:05 I/TestInvocation: Starting invocation for 'cts' on build '4.4_r1' on device 192.168.1.70:5555
05-19 17:35:05 I/192.168.
05-19 17:35:22 I/192.168.
05-19 17:35:24 I/192.168.
05-19 17:35:24 I/192.168.
05-19 17:35:24 I/192.168.
05-19 17:35:30 I/192.168.
05-19 17:35:32 I/192.168.
05-19 17:35:34 I/192.168.
05-19 17:35:37 I/192.168.
05-19 17:35:38 I/192.168.
05-19 17:35:41 I/192.168.
05-19 17:35:46 I/192.168.
05-19 17:35:46 I/192.168.
05-19 17:35:46 I/192.168.
05-19 17:35:46 I/192.168.
05-19 17:35:46 I/192.168.
05-19 17:35:46 I/192.168.
cts-tf >