More 2.0.4 results
"Wichmann, Mats D" <[email protected]> Tue, 22 Jun 2004 08:25:25 -0700
| Newsgroups | gmane.linux.lsb.implementation |
|---|---|
| Message-ID | <A06801158AE07847B27A52C1A074BC1D04C910F2__12298.5248839997$1087918083@fmsmsx404.amr.corp.intel.com> |
I had some interesting outcomes comparing results between ia64 "native" and ia64 lsbsi. Since these are running on top of the same kernel, and I've only selected differences, this /ought/ to factor out kernel issues from here. lsbsi now has a very recent glibc (June 8 cvs snapshot). So the open items are #4 and #5. Any thoughts on these? 1. these were supposed to be cleared up with the new glibc, and indeed they are: /tset/ANSI.os/time/ctime_X/T.ctime_X 1 FAIL,PASS /tset/ANSI.os/time/localtim_X/T.localtim_X 1 FAIL,PASS /tset/ANSI.os/time/mktime_X/T.mktime_X 1 FAIL,PASS 2. These are unapplied i18n patches, thus "expected" fails: /tset/LI18NUX2K.L1/utils/diff/diff 2 PASS,FAIL /tset/LI18NUX2K.L1/utils/egrep-tp/egrep-tp 5 PASS,FAIL /tset/LI18NUX2K.L1/utils/fgrep/fgrep 5 PASS,FAIL /tset/LI18NUX2K.L1/utils/grep-tp/grep-tp 5 PASS,FAIL /tset/LI18NUX2K.L1/utils/pr/pr 2 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 8 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 15 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 16 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 24 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 31 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 32 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 40 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 47 PASS,FAIL /tset/LI18NUX2K.L1/utils/sort/sort 48 PASS,FAIL 3. lsbsi has /media and /srv, the host does not: /tset/LSB.fhs/root/media/media-tc 1 FAIL,PASS /tset/LSB.fhs/root/media/media-tc 2 UNINITIATED,UNSUPPORTED /tset/LSB.fhs/root/media/media-tc 3 UNINITIATED,UNSUPPORTED /tset/LSB.fhs/root/media/media-tc 4 UNINITIATED,UNSUPPORTED /tset/LSB.fhs/root/media/media-tc 5 UNINITIATED,UNSUPPORTED /tset/LSB.fhs/root/srv/srv-tc 1 FAIL,PASS 4. These I don't know about. Why did the c_iflag tests go from unsupported to fail? What is it switching on to decide to run the tests? Why did the tcgetattr tests go to fail? =20 /tset/POSIX.os/devclass/c_iflag/T.c_iflag 6 UNSUPPORTED,FAIL /tset/POSIX.os/devclass/c_iflag/T.c_iflag 7 UNSUPPORTED,FAIL /tset/POSIX.os/devclass/c_iflag/T.c_iflag 8 UNSUPPORTED,FAIL /tset/POSIX.os/devclass/c_iflag/T.c_iflag 9 UNSUPPORTED,FAIL /tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 1 PASS,FAIL /tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 2 PASS,FAIL 5. Misc pthread tests. Does this indicate a bad build on the lsbsi? Or is this now a mismatch with an older kernel? /tset/PTHR.os/procprim/pthread_sigmask/T.pthread_sigmask 8 PASS,FAIL /tset/PTHR.os/procprim/pthread_sigmask/T.pthread_sigmask 9 PASS,FAIL /tset/PTHR.os/procprim/sigwait/T.sigwait 2 PASS,FAIL /tset/PTHR.os/thread/pthread_create/T.pthread_create 14 FAIL,PASS /tset/PTHR.os/thread/pthread_detach/T.pthread_detach 4 PASS,FAIL /tset/PTHR.os/thread/pthread_exit/T.pthread_exit 2 PASS,FAIL /tset/PTHR.os/thread/pthread_join/T.pthread_join 5 PASS,FAIL 6. the sigwait 5 test "hangs" (waits forever) when run under the lsbsi, killing off the testset means the final three testcases don't run - so this is a side effect. /tset/PTHR.os/procprim/sigwait/T.sigwait 6 PASS,MISSING /tset/PTHR.os/procprim/sigwait/T.sigwait 7 PASS,MISSING /tset/PTHR.os/procprim/sigwait/T.sigwait 8 UNTESTED,MISSING