cts test failed to execute on Lava Dashboard Linaro Android 4.4 TI-Panda daily builds

Bug #1266481 reported by Soumya Basak
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Won't Fix
Medium
HariGopal

Bug Description

Observed on Lava dashboard Linaro Android 4.4 Kitkat TI-Panda daily builds:

https://validation.linaro.org/dashboard/image-reports/linaro-android-member-ti_panda-linaro

with builds:
https://android-build.linaro.org/jenkins/job/linaro-android-member-ti_panda-linaro/522/
job_id: https://validation.linaro.org/scheduler/job/94559
lava_android_test_run cts test fail to execute on Daily builds:

error observed from the log report:

 LAVA: (stdout) <<<<<=========Log file [logcat.log] ends=========
 LAVA: try to reconnect the device(10.254.0.64:5555) 1/5 times
 LAVA: Begin to execute command: adb disconnect 10.254.0.64:5555
 LAVA: (stdout) No such device 10.254.0.64:5555
 LAVA: Begin to execute command: adb connect 10.254.0.64:5555
 LAVA: (stdout) unable to connect to 10.254.0.64:5555:5555
 LAVA: try to reconnect the device(10.254.0.64:5555) 2/5 times
 LAVA: Begin to execute command: adb disconnect 10.254.0.64:5555
 LAVA: (stdout) No such device 10.254.0.64:5555
 LAVA: Begin to execute command: adb connect 10.254.0.64:5555
 LAVA: (stdout) unable to connect to 10.254.0.64:5555:5555
 LAVA: try to reconnect the device(10.254.0.64:5555) 3/5 times
 LAVA: Begin to execute command: adb disconnect 10.254.0.64:5555
 LAVA: (stdout) No such device 10.254.0.64:5555
 LAVA: Begin to execute command: adb connect 10.254.0.64:5555
 LAVA: (stdout) unable to connect to 10.254.0.64:5555:5555
 LAVA: try to reconnect the device(10.254.0.64:5555) 4/5 times
 LAVA: Begin to execute command: adb disconnect 10.254.0.64:5555
 LAVA: (stdout) No such device 10.254.0.64:5555
 LAVA: Begin to execute command: adb connect 10.254.0.64:5555
 LAVA: (stdout) unable to connect to 10.254.0.64:5555:5555

<LAVA_DISPATCHER>2014-01-06 05:24:41 AM INFO: Execute adb command on host: adb disconnect 10.254.0.64:5555
 <LAVA_DISPATCHER>2014-01-06 05:24:41 AM WARNING: pexpect timed out, pass with status fail
 <LAVA_DISPATCHER>2014-01-06 05:24:41 AM WARNING: [ACTION-E] lava_android_test_run is finished with error (Failed to run test case(cts) on device(10.254.0.64:5555) with return value: 1).

ErrorMessage: Failed to run test case(cts) on device(10.254.0.64:5555) with return value: 1
 Lava failed at action lava_android_test_run with error:Failed to run test case(cts) on device(10.254.0.64:5555) with return value: 1

Traceback (most recent call last):
  File "/srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-12-05-f957fd5/lava_dispatcher/job.py", line 270, in run
  action.run(**params)
  File "/srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-12-05-f957fd5/lava_dispatcher/actions/lava_android_test.py", line 79, in run
  "value: %s" % (test_name, session.dev_name, rc))
 OperationFailed: Failed to run test case(cts) on device(10.254.0.64:5555) with return value: 1

Please look into the issue for QA Daily, weekly and monthly release test.

description: updated
description: updated
summary: - lava_android_test_run cts test fail on Lava Dashboard Linaro Android TI-
- Panda daily builds
+ cts test failed to execute on Lava Dashboard Linaro Android TI-Panda
+ daily builds
summary: - cts test failed to execute on Lava Dashboard Linaro Android TI-Panda
+ cts test failed to execute on Lava Dashboard Linaro Android 4.4 TI-Panda
daily builds
Changed in linaro-android:
assignee: nobody → HariGopal (harigopal-gollamudi)
vishal (vishalbhoj)
Changed in linaro-android:
importance: Undecided → Medium
Changed in linaro-android:
status: New → In Progress
Revision history for this message
Milosz Wasilewski (mwasilew) wrote :

The problem will be addressed with multi-node approach. For the moment CTS doesn't work correctly on lava dispatchers. Closing as won't fix as the solution is already available.

Changed in linaro-android:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.