RE: [Lsb-test] LSB 3.0 test results for Progeny Debian 3.0 PR2
>I have posted the results of running the LSB 3.0 test prereleases on
>Progeny Debian 3.0 PR2
Here are some very quick reactions. There doesn't look to be
a whole lot wrong here, once a few basics are cleared away.
1. lsbcmdchk:
lsbinstall 1 FAIL
-- old version of test, this command did not make the final 3.0 cut
and need not be provided.
2. libchk
libc.so.6 440 FAIL
libc.so.6 441 FAIL
libc.so.6 503 FAIL
libpthread.so.0 91 FAIL
libstdc++.so.6 3052 FAIL
libstdc++.so.6 3059 FAIL
Except the C++, these are all new symbols/versions (see the 3.0 release
notes: http://www.linuxbase.org/LSBWiki/ReleaseNotes3)
520|2 440 0 0 0|Did not find nftw (GLIBC_2.3.3) in libc.so.6
520|2 441 0 0 0|Did not find nftw64 (GLIBC_2.3.3) in libc.so.6
520|2 503 0 0 0|Did not find regexec (GLIBC_2.3.4) in libc.so.6
520|11 91 0 0 0|Did not find pthread_setschedprio (GLIBC_2.3.4) in
libpthread.so.0
The C++ errors have to do with virtual function pointers and
are not familiar.
3. runtime
The LI18NUX ones should be well known by now.
A lot of the others look familiar - as in we've seen
them other places, prior to various fixes. Some are
to the test suite -
Some quick notes:
/tset/POSIX.os/files/fpathconf/T.fpathconf 3 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 4 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 5 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 6 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 21 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 26 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 27 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 28 UNRESOLVED
/tset/POSIX.os/files/fpathconf/T.fpathconf 29 UNRESOLVED
/tset/POSIX.os/procenv/isatty_X/T.isatty_X 1 UNRESOLVED
These are all a failure to open /dev/pts/0 - basically,
a setup problem.
--
/tset/LSB.os/ioprim/readv_L/T.readv_L 21 UNRESOLVED
/tset/LSB.os/ioprim/writev_L/T.writev_L 16 UNRESOLVED
/tset/LSB.os/ioprim/writev_L/T.writev_L 25 UNRESOLVED
These were some kind of problem with the "no-space device"
(a loop-mounted file which is artificially filled nearly full).
--
/tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 4 FAIL
/tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 5 FAIL
These are setup problems. A newer version of the testsuite
(-4, the released version) should help getting these right.
--
/tset/ANSI.os/time/ctime_X/T.ctime_X 1 FAIL
/tset/ANSI.os/time/localtim_X/T.localtim_X 1 FAIL
/tset/ANSI.os/time/mktime_X/T.mktime_X 1 FAIL
Known glibc issue, should be fixed in upstream. Notes
on this before it had made it to upstream:
http://www.linuxbase.org/LSBWiki/TimeZoneFail
--
/tset/POSIX.os/files/stat_X/T.stat_X 1 FAIL
Failed to open /dev/sda, perhaps there isn't one (this is
the answer to an interview question on test setup - the
name of a block device that can be opened)
It's the value of VSX_BLKDEV_FILE in tetexec.cfg.
--
/tset/POSIX.os/procenv/getlogin/T.getlogin 1 FAIL
/tset/PTHR.os/procenv/getlogin_r/T.getlogin_r 1 FAIL
These come from running the test logged in as licquia
instead of the expected test user (vsx0)
4. C++
This one is common everywhere, and should make the waiver list.
/24_iterators/istreambuf_iterator/2.cc 1 FAIL
Reply to: