Re: Test cases that are possible candidates for a waiver
Hello,
I looked at the LSB-OS cases today, when running the testsuite on SuSE Linux 7.3.
On Tue, Dec 04, Kevin Caunt wrote:
> LSB-OS
>
> Testcase
>
> /tset/LSB.os/aio/aio_cancel/T.aio_cancel-4
[...]
> /tset/LSB.os/aio/lio_listio/T.lio_listio-9
I think we should remove the whole aio stuff. It does not work
on Linux.
> /tset/LSB.os/devclass/grantpt_L/T.grantpt_L-2
> /tset/LSB.os/devclass/grantpt_L/T.grantpt_L-3
I'm fixing this in the moment in current glibc.
> /tset/LSB.os/genuts/ftw/T.ftw-9
I have a patch for glibc for this.
> /tset/LSB.os/genuts/ftw_L/T.ftw_L-4
> /tset/LSB.os/genuts/ftw_L/T.ftw_L-6
> /tset/LSB.os/genuts/ftw_L/T.ftw_L-7
Looks all like this are all bugs in glibc which
are fixable.
> /tset/LSB.os/genuts/getopt/T.getopt-1
> /tset/LSB.os/genuts/getopt/T.getopt-4
I don't know about this one yet.
> /tset/LSB.os/genuts/nftw/T.nftw-14
> /tset/LSB.os/genuts/nftw/T.nftw-8
> /tset/LSB.os/genuts/nftw_L/T.nftw_L-4
> /tset/LSB.os/genuts/nftw_L/T.nftw_L-5
I think this one are fixed if somebody fixes ftw.
> /tset/LSB.os/genuts/openlog_L/T.openlog_L-2
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-100
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-115
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-2
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-28
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-5
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-6
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-61
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-7
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-85
> /tset/LSB.os/genuts/syslog_L/T.syslog_L-91
I don't understand why they fails, need to look deeper in it.
> /tset/LSB.os/ioprim/readv_L/T.readv_L-13
> /tset/LSB.os/ioprim/readv_L/T.readv_L-22
> /tset/LSB.os/ioprim/readv_L/T.readv_L-23
> /tset/LSB.os/ioprim/writev_L/T.writev_L-27
> /tset/LSB.os/ioprim/writev_L/T.writev_L-28
> /tset/LSB.os/ioprim/writev_L/T.writev_L-30
readv and writev looks like kernel bugs. Somebody else needs
to look at it.
> /tset/LSB.os/ipc/ftok_L/T.ftok_L-7
Don't understand why it fails, but looks like a glibc problem.
> /tset/LSB.os/ipc/msgctl/T.msgctl-14
> /tset/LSB.os/ipc/msgctl/T.msgctl-16
> /tset/LSB.os/ipc/msgrcv/T.msgrcv-5
> /tset/LSB.os/ipc/semctl/T.semctl-16
> /tset/LSB.os/ipc/shmdt/T.shmdt-2
> /tset/LSB.os/jump/makecontext/T.makecontext-1
> /tset/LSB.os/jump/makecontext/T.makecontext-2
> /tset/LSB.os/jump/makecontext/T.makecontext-3
Don't know about the above.
> /tset/LSB.os/libdl/dlopen/T.dlopen-12
> /tset/LSB.os/libdl/dlopen/T.dlopen-4
Did somebody run the test with a current glibc cvs snapshot?
This one could be fixed, but I'm not sure.
> /tset/LSB.os/mfiles/mmap_P/T.mmap_P-34
> /tset/LSB.os/mfiles/msync/T.msync-1
> /tset/LSB.os/mfiles/msync_P/T.msync_P-7
> /tset/LSB.os/mfiles/msync_P/T.msync_P-8
> /tset/LSB.os/mfiles/munmap_P/T.munmap_P-1
> /tset/LSB.os/mfiles/munmap_P/T.munmap_P-2
> /tset/LSB.os/mfiles/munmap_P/T.munmap_P-3
> /tset/LSB.os/mfiles/munmap_P/T.munmap_P-4
> /tset/LSB.os/mfiles/munmap_P/T.munmap_P-5
> /tset/LSB.os/procenv/chroot/T.chroot-7
> /tset/LSB.os/procenv/nice/T.nice-5
> /tset/LSB.os/procenv/nice/T.nice-6
> /tset/LSB.os/procenv/nice/T.nice-7
> /tset/LSB.os/procenv/nice/T.nice-8
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE GmbH Deutschherrenstr. 15-19 D-90429 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
Reply to: