Analysis of LSB.os results
All,
For your information Here is an analysis of the results that we obtained
when the LSB.os test cases were run on our Debian Linux 2.4 system.
(We used the kernel-source-2.4.2 Debian package)
We'd appreciate comments. Some features should probably
be optional and not tested by default (for example some of
the tests relying on shm_open()).
Tests that gave a FAIL result
-----------------------------
/tset/ANSI.hdr/misc/time/T.time{4,29}
CLK_TCK is not defined in the header. The definition has been
commented out as obsolete.
Also a problem with sigevent because POSIX199309 is not switched on
by XOPEN_SOURCE 500
/tset/ANSI.os/streamio/fopen/T.fopen{25}
ENAMETOOLONG problem
/tset/ANSI.os/streamio/freopen/T.freopen{26}
ENAMETOOLONG problem
/tset/ANSI.os/streamio/printf/T.fprintf{27,31,35,47}
/tset/ANSI.os/streamio/printf/T.printf{27,31,35,47}
/tset/ANSI.os/streamio/printf/T.sprintf{27,31,35,47}
All %.S format string problems
/tset/ANSI.os/streamio/remove/T.remove{7,14}
Test 7 - common problem with rename and unlink.
Not certain of cause - may be parameter setting.
Test 14 - ENAMETOOLONG problem
/tset/ANSI.os/streamio/scanf/T.fscanf{25,26,41}
/tset/ANSI.os/streamio/scanf/T.scanf{25,26,41}
/tset/ANSI.os/streamio/scanf/T.sscanf{25,26,41}
All %.S format string problems
/tset/ANSI.os/streamio/tmpfile/T.tmpfile{2}
Looks like a system fault.
/tset/ANSI.os/streamio/vprintf/T.vfprintf{27,31,35,47}
/tset/ANSI.os/streamio/vprintf/T.vprintf{27,31,35,47}
/tset/ANSI.os/streamio/vprintf/T.vsprintf{27,31,35,47}
All %.S format string problems
/tset/POSIX.hdr/misc/dirent/T.dirent{2,6}
Not clear on the cause of this problem
/tset/POSIX.hdr/misc/general/T.general{1}
This is a set-up issue on the system running the tests.
Please ignore this failure.
/tset/POSIX.hdr/misc/limits/T.limits{3}
Header file problem with _POSIX limits
/tset/POSIX.hdr/misc/signal/T.signal{39}
Not clear on the cause of this problem
/tset/POSIX.hdr/misc/wait/T.wait{10}
Same problem as signal header 39.
/tset/POSIX.os/devclass/c_iflag/T.c_iflag{19}
/tset/POSIX.os/devclass/c_lflag/T.c_lflag{6}
/tset/POSIX.os/devclass/tcdrain/T.tcdrain{2}
/tset/POSIX.os/devclass/tcsetattr/T.tcsetattr{3,8}
These problems relate to the use of pttys
/tset/POSIX.os/devclass/tcsetpgrp/T.tcsetpgrp{6}
Error condition problem.
/tset/POSIX.os/files/access/T.access{38}
/tset/POSIX.os/files/chdir/T.chdir{7}
/tset/POSIX.os/files/chmod/T.chmod{12}
/tset/POSIX.os/files/chown/T.chown{11}
/tset/POSIX.os/files/creat/T.creat{23}
/tset/POSIX.os/files/link/T.link{17}
/tset/POSIX.os/files/mkdir/T.mkdir{14}
/tset/POSIX.os/files/mkfifo/T.mkfifo{12}
/tset/POSIX.os/files/open/T.open{37}
/tset/POSIX.os/files/opendir/T.opendir{10}
/tset/POSIX.os/files/pathconf/T.pathconf{21}
ENAMETOOLONG problem
/tset/POSIX.os/files/rename/T.rename{13,27}
Test 13 is the same problem as remove test 7.
Test 27 is ENAMETOOLONG problem
/tset/POSIX.os/files/rmdir/T.rmdir{7,15}
Test 7 is the same problem as remove test 7.
Test 15 is ENAMETOOLONG problem
/tset/POSIX.os/files/stat/T.stat{9}
ENAMETOOLONG problem
/tset/POSIX.os/files/unlink/T.unlink{14,19}
Test 14 ENAMETOOLONG problem
Test 19 is an error value problem.
/tset/POSIX.os/files/utime/T.utime{13}
ENAMETOOLONG problem
/tset/POSIX.os/ioprim/fcntl/T.fcntl{37}
Error value problem
/tset/POSIX.os/ioprim/read/T.read{13}
Looks like a system problem.
/tset/POSIX.os/ioprim/write/T.write{2}
Looks like a system problem.
/tset/POSIX.os/procenv/setpgid/T.setpgid{8}
Looks like a system problem.
/tset/POSIX.os/procenv/sysconf/T.sysconf{10}
Looks like a system problem.
/tset/POSIX.os/procprim/exec/T.execl{37}
/tset/POSIX.os/procprim/exec/T.execle{37}
/tset/POSIX.os/procprim/exec/T.execlp{37}
/tset/POSIX.os/procprim/exec/T.execv{37}
/tset/POSIX.os/procprim/exec/T.execve{37}
/tset/POSIX.os/procprim/exec/T.execvp{37}
All ENAMETOOLONG problems.
/tset/POSIX.os/procprim/sigconcept/T.sigconcept{10,35}
Test 10 looks like a system problem.
Test 35 is associated with tcdrain and may relate to the use of psuedo
ttys.
/tset/LSB.os/aio/aio_cancel/T.aio_cancel{4,7}
/tset/LSB.os/aio/aio_fsync/T.aio_fsync{10}
/tset/LSB.os/aio/aio_read/T.aio_read{12}
/tset/LSB.os/aio/aio_return/T.aio_return{3}
/tset/LSB.os/aio/aio_suspend/T.aio_suspend{4,5}
/tset/LSB.os/aio/aio_write/T.aio_write{13,14}
Not investigated in depth, but seem to be system problems.
/tset/LSB.os/aio/lio_listio/T.lio_listio{1,2,3,4,5,6,9,10,11,12,15,16,17,18,21,24,25,26,27,28,31,33,34,35,36,37,38,40,41,42}
The constant _SC_AIO_LISTIO_MAX is not defined in unistd.h.
/tset/LSB.os/devclass/grantpt_L/T.grantpt_L{2,3}
These look like wrongly reported error conditions.
/tset/LSB.os/files/telldir_L/T.telldir_L{1}
Looks like a system problem.
/tset/LSB.os/genuts/ftw/T.ftw{9}
ENAMETOOLONG problem.
/tset/LSB.os/genuts/ftw_L/T.ftw_L{4,6,7}
Looks like a system problem.
/tset/LSB.os/genuts/getopt/T.getopt{1}
Looks like a system problem.
/tset/LSB.os/genuts/nftw/T.nftw{14}
ENAMETOOLONG problem.
/tset/LSB.os/genuts/nftw_L/T.nftw_L{4,5}
Same as ftw_L tests 6 and 7.
/tset/LSB.os/genuts/openlog_L/T.openlog_L{2}
Looks like a system problem.
/tset/LSB.os/genuts/syslog_L/T.syslog_L{2,5,6,7,28,85,91,100,101,102,103,104,105,106,107,113,115,117}
There seems to a be a problem in the printing routines causing many of
these errors. Does syslog() call the same underlying code as sprintf()?
/tset/LSB.os/ioprim/readv_L/T.readv_L{13,22,23}
/tset/LSB.os/ioprim/writev_L/T.writev_L{2,27,28,30}
Look like system problems. Some errors duplicate those seen in the
read() and write() system calls.
/tset/LSB.os/ipc/ftok_L/T.ftok_L{7}
Looks like a system problem.
/tset/LSB.os/ipc/msgctl/T.msgctl{14,16}
/tset/LSB.os/ipc/msgrcv/T.msgrcv{5}
/tset/LSB.os/ipc/semctl/T.semctl{16}
/tset/LSB.os/ipc/shmctl/T.shmctl{16}
/tset/LSB.os/ipc/shmdt/T.shmdt{2}
/tset/LSB.os/jump/getcontext/T.getcontext{1,2}
/tset/LSB.os/libdl/dlopen/T.dlopen{4,12}
These all look like system problems.
/tset/LSB.os/mfiles/mmap/T.mmap{1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,26,31}
/tset/LSB.os/mfiles/mmap_P/T.mmap_P{34}
/tset/LSB.os/mfiles/mmap_X/T.mmap_X{1,2}
/tset/LSB.os/mfiles/msync/T.msync{1}
/tset/LSB.os/mfiles/msync_P/T.msync_P{1,2,3,4,5,7,8}
/tset/LSB.os/mfiles/munmap/T.munmap{1}
/tset/LSB.os/mfiles/munmap_P/T.munmap_P{1,2,3,4,5}
/tset/LSB.os/mfiles/munmap_X/T.munmap_X{1}
Most of these failures relate to the fact that shm_open() returns
ENOSYS.
The msync_P failures occured because of a test suite set-up problem.
Rerunning these tests gave failures only on tests 7 & 8 which look as
if they are system problems.
/tset/LSB.os/mprotect/mprotect_P/T.mprotect_P{8,9}
These look like system problems.
/tset/LSB.os/procenv/chroot/T.chroot{7}
ENAMETOOLONG problem
/tset/LSB.os/procenv/cuserid/T.cuserid{3}
Looks like a system problem.
/tset/LSB.os/procenv/nice/T.nice{5,6,7,8}
Looks like a system problem.
/tset/LSB.os/time/strptime/T.strptime{3}
Looks like a system problem.
total 224
Tests that gave an UNRESOLVED result
------------------------------------
/tset/ANSI.os/streamio/freopen/T.freopen{38,39}
Not sure of the cause, needs more investigation.
/tset/POSIX.os/dataform/cpio/T.cpio{1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28}
/tset/POSIX.os/dataform/tar/T.tar{1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38}
The pax package was not installed.
/tset/POSIX.os/devclass/i_close/T.i_close{1}
/tset/POSIX.os/devclass/i_spchars/T.i_spchars{1,3,5,14,17}
/tset/POSIX.os/devclass/tcdrain/T.tcdrain{7}
/tset/POSIX.os/devclass/tcflow/T.tcflow{2,6,7,8,13,14,15,16}
/tset/POSIX.os/devclass/tcflush/T.tcflush{1,2,3,4,5,6,10,11,12,13}
/tset/POSIX.os/devclass/tcsetattr/T.tcsetattr{1,13}
These all relate to the use of psuedo ttys.
/tset/POSIX.os/files/creat/T.creat{11}
/tset/POSIX.os/files/open/T.open{16}
Looks like a system problem
/tset/POSIX.os/procenv/sysconf/T.sysconf{3}
CLK_TCK not in time.h header.
/tset/POSIX.os/procprim/sigconcept/T.sigconcept{30,31,34,36,37}
These may all relate to the use of psuedo ttys.
/tset/LSB.os/aio/aio_fsync/T.aio_fsync{8}
/tset/LSB.os/files/dev_tty/T.dev_tty{1}
These look like system problems.
/tset/LSB.os/genuts/getopt/T.getopt{4}
There is both a system problem and a code fault which gives a path
trace error.
/tset/LSB.os/genuts/nftw/T.nftw{8}
/tset/LSB.os/genuts/syslog_L/T.syslog_L{61}
These look like system problems.
/tset/LSB.os/jump/makecontext/T.makecontext{1,2,3}
/tset/LSB.os/jump/setcontext/T.setcontext{1}
These depend on getcontext which is returning ENOSYS.
total 111
best regards
Andrew Josey
The Open Group
Reply to: