Test cases "methanol", "mmtest" ,"wifi" "chrome","pm-qa","cts" fails on panda Linaro-android Lava dashboard image report

Bug #1133384 reported by Soumya Basak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Won't Fix
Undecided
Unassigned

Bug Description

image link: https://android-build.linaro.org/jenkins/job/linaro-android-member-ti_panda-linaro/208/
job details: http://validation.linaro.org/lava-server/scheduler/job/48468
complete log: http://validation.linaro.org/lava-server/scheduler/job/48468/log_file

log:

mmtest fail on device getting from the log

[ 5798.424835] binder: release proc 5709, transaction 289134, not freed
[ 5798.443023] binder: release proc 5709, transaction 289140, not freed
[ 5798.919982] binder: 1808:1823 transaction failed 29189, size 52-0
[ 5798.937530] binder: 1808:1823 transaction failed 29189, size 52-0
[ 5798.954467] binder: 1808:1823 transaction failed 29189, size 52-0
[ 5798.970825] binder: 1808:1823 transaction failed 29189, size 52-0
[ 5798.987548] binder: 1808:1823 transaction failed 29189, size 52-0
[ 5804.535827] omapfb omapfb: Unknown ioctl 0x5401

wifi test from the device is failed getting from the log

[ 5850.225067] wl1271: loaded
[ 5850.965484] wl1271: firmware booted (Rev 6.3.0.0.77)
[ 5850.983978] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 5860.039794] wl1271: down
[ 5865.316162] wl1271: loaded
[ 5866.122863] wl1271: firmware booted (Rev 6.3.0.0.77)
[ 5866.157226] ADDRCONF(NETDEV_UP): wlan0: link is not ready

methanol test ont the device is failed from the log

[ 6939.718414] binder: 2246:2246 transaction failed 29189, size 92-0
[ 6943.501281] omapfb omapfb: Unknown ioctl 0x5401

chrome test on the device is not finished yet getting from the log:

<LAVA_DISPATCHER>2013-02-20 05:22:09 PM INFO: waiting for TIME_WAIT 5555 socket to finish
<LAVA_DISPATCHER>2013-02-20 05:22:12 PM INFO: waiting for TIME_WAIT 5555 socket to finish
<LAVA_DISPATCHER>2013-02-20 05:22:15 PM WARNING: device already powered on, powering off first

pm-qa test on the target is failed getting from the log

<LAVA_DISPATCHER>2013-02-20 05:24:37 PM INFO: [ACTION-B] lava_android_test_run is started with {'timeout': 18000, u'test_name': u'pm-qa'}
root@linaro# <LAVA_DISPATCHER>2013-02-20 05:24:37 PM INFO: adb connect over default network interface
LC_ALL=C ping -W4 -c1 19[ 120.494079] binder: 1355:1874 transaction failed 29189, size 12-0
[ 120.513793] binder: send failed reply for transaction 8666, target dead

[ 407.698272] DSSCOMP: blanked screen
[ 441.727844] init: untracked pid 3201 exited
[ 441.736602] init: untracked pid 3175 exited
[ 441.745147] init: untracked pid 3174 exited

cts test on the device is failed getting from the log

<LAVA_DISPATCHER>2013-02-20 05:51:07 PM INFO: Execute command on host: timeout 18000s lava-android-test run cts -s 192.168.30.234:5555 -o /tmp/tmpMIZmwH/cts.2013-02-20T17:51:07Z.bundle
[ 183.180786] omapfb omapfb: Unknown ioctl 0x5401

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
the same issue is observed with the Linaro-android panda builds
https://android-build.linaro.org/jenkins/job/linaro-android-member-ti_panda-linaro/248/
job id: http://validation.linaro.org/lava-server/scheduler/job/50361
complete log: http://validation.linaro.org/lava-server/scheduler/job/50361/log_file

the same issue is reproduced with the builds
https://android-build.linaro.org/jenkins/job/linaro-android-member-ti_panda-linaro/250/
jobid: http://validation.linaro.org/lava-server/scheduler/job/50415
complete log: http://validation.linaro.org/lava-server/scheduler/job/50415/log_file

summary: - Linaro android daily tests "methanol", "mmtest" ,"wifi" "chrome","pm-
- qa","cts" fails on panda Linaro-android Lava dashboard image report
+ Test cases "methanol", "mmtest" ,"wifi" "chrome","pm-qa","cts" fails on
+ panda Linaro-android Lava dashboard image report
Revision history for this message
Soumya Basak (soumya-basak) wrote :

on
builds: https://android-build.linaro.org/jenkins/job/linaro-android-member-ti_panda-linaro/212/
job id: http://validation.linaro.org/lava-server/scheduler/job/48831
complete log: http://validation.linaro.org/lava-server/scheduler/job/48831/log_file

observed from the Lava daily dashboard panda Linaro android test cases
Looper-test send message delay is failed:

frameworks/native/libs/utils/tests/Looper_test.cpp:518: Failure
The difference between 100 + 100 and elapsedMillis is 161, which exceeds 25, where
100 + 100 evaluates to 200,
elapsedMillis evaluates to 361, and
25 evaluates to 25.
third poll should timeout

Revision history for this message
Soumya Basak (soumya-basak) wrote :

observed on builds:
https://android-build.linaro.org/jenkins/job/linaro-android-member-ti_panda-linaro/212/
job id: http://validation.linaro.org/lava-server/scheduler/job/48831
complete log: http://validation.linaro.org/lava-server/scheduler/job/48831/log_file
from the dashboard report:
*command ashmemtest*, *CHROME*, *skia* test is not executed and not tested yet.

description: updated
description: updated
Revision history for this message
Soumya Basak (soumya-basak) wrote :
Revision history for this message
Soumya Basak (soumya-basak) wrote :

we file a new bugs for each seperate test-cases (1 bug = 1 test-cases),

for example cts test cases: https://bugs.launchpad.net/linaro-android/+bug/1178565
so, make this bugs "invalid".

Revision history for this message
Soumya Basak (soumya-basak) wrote :

Please refer to the bug: https://bugs.launchpad.net/linaro-android/+bug/1191668

and make the status of this bug : "Wont Fix"/"invalid".

Revision history for this message
Soumya Basak (soumya-basak) wrote :

for cts test please refer to the bug: https://bugs.launchpad.net/linaro-android/+bug/1178565

Revision history for this message
Soumya Basak (soumya-basak) wrote :

for mmtest please refer to the bug: https://bugs.launchpad.net/linaro-android/+bug/1190941
pm-qa test suites: https://bugs.launchpad.net/linaro-android/+bug/1191703
chrome, wifi, & methanol tests suites are stable now.

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

Other bug subscribers

Remote bug watches

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