Re: Answer to common failures?
At 2002/7/18 15:07-0700 Wichmann, Mats D writes:
>
> ************************************************************************
> /tset/LSB.os/devclass/grantpt_L/T.grantpt_L 2 Failed
>
> Test Information:
> grantpt(5) did not give correct results
> ERRNO VALUES: expected: 9 (EBADF), observed: 25 (ENOTTY)
>
>
> ************************************************************************
> /tset/LSB.os/devclass/grantpt_L/T.grantpt_L 3 Failed
>
> Test Information:
> grantpt(5) did not give correct results
> ERRNO VALUES: expected: 22 (EINVAL), observed: 25 (ENOTTY)
Are you running the tests using something like screen?
> ************************************************************************
> /tset/LSB.os/genuts/ftw/T.ftw 4 Failed
>
> Test Information:
> ftw(./ftw_d.1, ..., 2) returned -1 instead of 0
> ftw did not call function with argument FTW_DNR
> although the root of the file tree given was
> read-only
>
>
> ************************************************************************
> /tset/LSB.os/genuts/nftw/T.nftw 10 Failed
>
> Test Information:
> ftw(./ftwD1/ftw_d.1, ..., 2) returned -1 instead of 0
> ftw did not call function with argument FTW_DNR
> although the root of the file tree given was
> read-only
I think these 2 have been fixed in glibc CVS (Thorsten would know better).
> ************************************************************************
> /tset/LSB.os/ioprim/readv_L/T.readv_L 24 Failed
>
> Test Information:
> iov[0].iov_base = 0x4013d008, iov[0].iov_len = 2098176
> iov[1].iov_base = 0x4013d008, iov[1].iov_len = 2098176
> iov[2].iov_base = 0x4013d008, iov[2].iov_len = 2098176
> ...(lines omitted)
> iov[1022].iov_base = 0x4013d008, iov[1022].iov_len = 2098176
> iov[1023].iov_base = 0x4013d008, iov[1023].iov_len = 2098176
> readv(5, iov, 1024) did not behave as expected
> RETURN VALUES: expected: -1, observed: 36
> ERRNO VALUES: expected: 22 (EINVAL), observed: 0 (NO ERROR)
>
>
> ************************************************************************
> /tset/LSB.os/ioprim/writev_L/T.writev_L 30 Failed
>
> Test Information:
> iov[0].iov_base = 0x4013d008, iov[0].iov_len = 2098176
> iov[1].iov_base = 0x4013d008, iov[1].iov_len = 2098176
> iov[2].iov_base = 0x4013d008, iov[2].iov_len = 2098176
> ...(lines omitted)
> iov[1022].iov_base = 0x4013d008, iov[1022].iov_len = 2098176
> iov[1023].iov_base = 0x4013d008, iov[1023].iov_len = 2098176
> writev(7, iov, 1024) did not behave as expected:
> RETURN VALUES: expected: -1, observed: 2147483647
> ERRNO VALUES: expected: 22 (EINVAL), observed: 0 (NO ERROR)
These two are in the FAQ (kernel fixes).
http://www.linuxbase.org/test/lsb-runtime-test-faq.html
Incidentally I believe Alan Cox now has a different fix for these that
went into 2.5.
Regards,
Chris
--
cyeoh@au.ibm.com
IBM OzLabs Linux Development Group
Canberra, Australia
--
To UNSUBSCRIBE, email to lsb-impl-request@lists.linuxbase.org
with subject of "unsubscribe". Trouble? Email listmaster@lists.linuxbase.org
Reply to: