Qemux86-ltp: Difference between revisions
(→1.0/M2) |
(→1.0/M2) |
||
Line 1: | Line 1: | ||
==1.0/M2== | ==1.0/M2== | ||
total: 34 (100% audited) | '''total: 34 (100% audited)''' | ||
*LTP: 2 | *LTP: 2 |
Revision as of 08:20, 30 January 2011
1.0/M2
total: 34 (100% audited)
- LTP: 2
- NAB: 26
- Fixed: 6
pending: 0
not started: 0
LTP cases | status | owner | error msg | lsb | comment | bugzilla |
lchown02 | LTP | Kevin Tian | Fail to modify tfile_1 ownership(s) | Fail to modify tfile_1 ownership(s) | n/a | n/a |
lchown02_16 | LTP | Kevin Tian | Fail to modify tfile_1 ownership(s) | Fail to modify tfile_1 ownership(s) | n/a | n/a |
ld | Fixed | Kevin Tian | ld01: line 149: file: not found; FAIL - ld failed to build a shared object | ld01: line 75: gcc: not found | PASS after copying 'file' utility to SDK profile
but I'm not sure whether we want to pull this into SDK profile. |
[bug676] |
ldd | Fixed | Kevin Tian | ldd01: line 99: file: not found; ldd01: line 100: ldd: not found | dd01: line 99: gcc: not found | PASS after copying 'ldd' utility to SDK profile
ldd package is actually generated already. this one is good to be included into SDK profile as a development utility |
[bug676] |
chroot01 | Fixed | Kevin Tian | Received unexpected error - 13 : Permission denied | PASS | this case expects an -EPERM (if /var is set with 755 permission bits), but not sure why SDK image in M2 has the permission bits of /var as 0700 which results -EACCES returned. latest master has no this issue. will monitor in later tests. | n/a |
mtest06 | Fixed | Kevin Tian | caught unexpected signal - 11 --- exiting | same error in lsb | PASS in 01/11 nightly test
will recheck in next milestone test |
n/a |
at_deny01 | Fixed | Kevin Tian | TCONF : at command not found on system | at_deny01: line 194: /etc/init.d/atd: not found | similar reason as cron_deny01, that we don't have a right environment for normal user to use at. | [bug675]
bug5 |
at_allow01 | Fixed | Kevin Tian | TCONF : at command not found on system | at_allow01: line 185: /etc/init.d/atd: not found | similar reason as cron_deny01, that we don't have a right environment for normal user to use at. | [bug675]
bug5 |
cron | NAB | Kevin Tian | cron_tests.sh: line 102: crontab: not found; tail: cannot open `/var/log/messages' for reading: No such file or directory | crontab activity not recorded in /var/log/messages. | in yocto crontab is recorded in /var/log/sysctl | n/a |
ioctl03 | NAB | Kevin Tian | Error Opening /dev/net/tun: No such file or directory | Error Opening /dev/net/tun: No such file or directory | tun is an optional kernel feature, not included in the kernel config for current profile | n/a |
unzip01 | NAB | Kevin Tian | unzip output differs from expected output. Details | PASS | busybox has a different output format | n/a |
syslog01 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: *.crit: not found; /var/log/maillog no such log file | PASS | n/a | n/a |
syslog02 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: mail.emerg: not found; /var/log/maillog no such log file | PASS | n/a | n/a |
syslog03 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: daemon.info: not found; /var/log/messages no such log file | PASS | n/a | n/a |
syslog04 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: user.info: not found; /var/log/messages no such log file | PASS | n/a | n/a |
syslog05 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: user.info: not found; /var/log/messages no such log file | PASS | n/a | n/a |
syslog07 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: user.debug: not found; grep: /var/log/messages: No such file or directory | PASS | n/a | n/a |
syslog08 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: user.info: not found; /var/log/messages no such log file | PASS | n/a | n/a |
syslog09 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: user.debug: not found; /var/log/messages no such log file | PASS | n/a | n/a |
syslog10 | NAB | Kevin Tian | /etc/init.d/syslog: /etc/syslog.conf: line 2: user.debug: not found; /var/log/messages no such log file | PASS | n/a | n/a |
tar | NAB | Kevin Tian | tar_tests.sh: line 172: file: not found; tar: zcvf option failed to create a compressed tar file | PASS | busybox supports less options than standard tar | n/a |
gzip01 | NAB | Kevin Tian | gzip: invalid option -- 'r' | PASS | busybox doesn't support "-r" option | n/a |
cpio | NAB | Kevin Tian | cpio: invalid option -- 'o' | PASS | busybox doesn't support "-o" option | n/a |
logrotate | NAB | Kevin Tian | INIT: command logrotate not found | PASS | n/a | n/a |
file | NAB | Kevin Tian | file_test.sh: line 162: file: not found | home/root/ltp/ltp/tmp/cprog: cannot open `/home/root/ltp/ltp/tmp/cprog' (No such file or directory); file09 9 TBROK : rpm command broke. Reason:warning: Could not canonicalize hostname: qemux86; error: Could not open /usr/src/rpm/SRPMS/cprog-0.0.7-3.src.rpm: No such file or directory | two reasons for LSB failure:
a) LTP's own problem - there's no check whether /usr/src/rpm/SRPM exists or not, which contributes to "No such file or directory" error; b) rpm5 has different output as rpm.org. "RPM v3.0 bin" is generated while "RPM v3.0 src" is expected |
n/a |
open08 | NAB | Kevin Tian | unexpected error - 13 : Permission denied - expected 21 | PASS | n/a | n/a |
mmapstress06 | NAB | Kevin Tian | mmapstress06: errno = 12; large mmap failed for this test to run, it needs a mmap space of 32769 pages | same in lsb | PASS with "-m 512". not enough free memory. at least 128M is required. | n/a |
mtest06_2 | NAB | Kevin Tian | main(): mmap(): Cannot allocate memory | same error in lsb | PASS by enlarging memory size to 1278M, because this test case requires 1G free memory | n/a |
cron_deny01 | NAB | Kevin Tian | Could not add test user c01_user to system | /bin/sh: cron_deny01: not found | SDK profile doesn't contain cron;
LSB profile has multiple issues: 1) lsb's own error (use /var/spool/cron/deny while /etc/cron.deny is expected by cronie) 2) PATH contains ending colon which results "cron_deny01 not found" error 3) cronie itself lacks of necessary files and permissions to support non-root user using crontab |
[bug672]
[bug673] |
cron_allow01 | NAB | Kevin Tian | cron_allow01: line 200: useradd: not found | /bin/sh: cron_allow01: not found | same reason as cron_deny01 | [bug672]
[bug673] |
cron02 | NAB | Kevin Tian | cron02: line 79: useradd: not found;Could not add test user c01_user to system | /bin/sh: cron_pos_tests.sh: not found | same reason as cron_deny01
and one more specific reason. LTP cron test assumes vixie-cron behavior, which allows any user to use crontab if there's no /etc/cron.deny and /etc/cron.allow. cronie however enforces the reverse, that only superuser is allowed under that condition. LTP test case needs to be enhanced to explicitly set cron.allow before the test. |
report to LTP
[bug672] [bug673] |
cron_dirs_checks01 | NAB | Kevin Tian | FAIL: /etc/cron.d. Could not obtain directory status | FAIL: /etc/cron.d. Could not obtain directory status | lack of necessary directories, like cron.monthly, ...
but there's also one known issue. this case requires no write permission for group/other users, however we have to keep write permission for crontab user for /var/spool/cron to make crontab working correctly. So this case is known to fail in the future too |
[bug672]
[bug673] |
su01 | NAB | Kevin Tian | su01: line 175: userdel: not found | sh: /home/root/ltp/ltp/testcases/bin/su01_s1: not found | su01_s1 uses '/usr/bin/expect' as the interpreter, which I don't think needs to add into yocto. so this will remain as a failure
there's one issue though, that /bin/sh is still linked to busybox even when bash is included in LSB profile, which makes the error message inaccurate. with bash the error becomes "/usr/bin/expect: bad interpreter" |
[bug674] |
sysctl03 | NAB | Kevin Tian | TWARN : this test's results are based on potentially undocumented behavior in the kernel. read the NOTE in the source file for more details | TWARN : this test's results are based on potentially undocumented behavior in the kernel. read the NOTE in the source file for more details | TWARN is not a failure, especially in this case sysctl03 throws out the warning when the kernel version >2.6.32.
since we have 2.6.37, this is expected |
n/a |