More runtime 2.0.2 / lsbsi investigation

"Wichmann, Mats D" <[email protected]> Mon, 3 May 2004 10:56:54 -0700
Newsgroups gmane.linux.lsb.implementation
Message-ID <[email protected]>
Following on to last week's posting, I also wanted to post the
difference
between running lsb-runtime-test 2.0.2 on the same ia64 platform twice,
once natively and once inside an lsbsi-chroot.

After starting to work through the differences I saw so many in common
with the ones I saw on x86_64 that I switched gears and instead
generated
a difference between the 2.0.2 runs in the lsbsi on the two machines.

This is a small list, so it's clear to me there are some significant
common failures between the two lsbsi builds.  These are reportedly not
being seen on other platforms.


$ tjreport lsbsi-ia64.journal lsbsi-x86_64.journal
/tset/ANSI.os/streamio/freopen/T.freopen 13 PASS,FAIL
/tset/LSB.fhs/linux/lib64/lib64-tc 2 UNSUPPORTED,FAIL
/tset/LSB.fhs/root/lib/lib-tc 3 PASS,FAIL
/tset/LSB.fhs/root/lib/lib-tc 4 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 9 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 16 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 18 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 19 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 20 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 21 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 23 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 24 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 29 PASS,FAIL
/tset/LSB.os/ioprim/writev_L/T.writev_L 30 PASS,FAIL
/tset/POSIX.os/files/utime/T.utime 3 FAIL,PASS
/tset/POSIX.os/files/utime/T.utime 4 FAIL,PASS
/tset/POSIX.os/files/utime/T.utime 6 FAIL,PASS
/tset/POSIX.os/ioprim/write/T.write 16 PASS,FAIL
/tset/POSIX.os/procenv/sysconf/T.sysconf 8 FAIL,PASS
/tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 11 FAIL,PASS
/tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 13 FAIL,PASS
/tset/POSIX.os/procenv/times/T.times 3 PASS,FAIL
/tset/POSIX.os/procenv/times/T.times 5 PASS,UNINITIATED
/tset/PTHR.os/procenv/ttyname_r/T.ttyname_r 2 PASS,FAIL
/tset/PTHR.os/sysdb/getpwuid_r/T.getpwuid_r 3 PASS,FAIL
/tset/PTHR.os/thread/pthread_exit/T.pthread_exit 2 FAIL,PASS

Of that list, thefollowing are "worse" results on ia64's lsbsi, included
with their journal snippets:

/tset/POSIX.os/files/utime/T.utime 3 FAIL,PASS
/tset/POSIX.os/files/utime/T.utime 4 FAIL,PASS
/tset/POSIX.os/files/utime/T.utime 6 FAIL,PASS
All three of the above look like this (time is one tick less than
the expected/allowed range):
200|415 3 07:47:22|TP Start
520|415 3 00007633 1 1|successful call to utime("utime-t.3", NULL) did
not set st_atime correctly
520|415 3 00007633 1 2|expected 1083595645-1083595646, observed
1083595644
520|415 3 00007633 1 3|successful call to utime("utime-t.3", NULL) did
not set st_mtime correctly
520|415 3 00007633 1 4|expected 1083595645-1083595646, observed
1083595644
520|415 3 00007633 1 5|successful call to utime("utime-t.3", NULL) did
not set st_atime correctly
520|415 3 00007633 1 6|expected 1083595647-1083595648, observed
1083595646
520|415 3 00007633 1 7|successful call to utime("utime-t.3", NULL) did
not set st_mtime correctly
520|415 3 00007633 1 8|expected 1083595647-1083595648, observed
1083595646
220|415 3 1 07:47:27|FAIL


/tset/POSIX.os/procenv/sysconf/T.sysconf 8 FAIL,PASS
200|474 8 07:58:17|TP Start
520|474 8 00007908 1 1|sysconf(_SC_VERSION) failed expected 200112, got
199506
220|474 8 1 07:58:17|FAIL

/tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 11 FAIL,PASS
/tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 13 FAIL,PASS
These two have identical failures:
520|475 11 00007909 1 1|sysconf(_SC_2_VERSION) failed expected 200112 -
got 199209
220|475 11 1 07:58:18|FAIL


/tset/PTHR.os/thread/pthread_exit/T.pthread_exit 2 FAIL,PASS
200|1011 2 11:09:43|TP Start
520|1011 2 00012958 1 1|A successful call to pthread_exit(value_ptr)
performs the
520|1011 2 00012958 1 2|following actions in order:
520|1011 2 00012958 1 3|a) each cancellation cleanup handler registered
for the exiting
520|1011 2 00012958 1 4|thread is called in last-registered,
first-called order.
520|1011 2 00012958 1 5|b) each thread-specific data destructor function
registered for
520|1011 2 00012958 1 6|the exiting thread is called in unspecified
order.
520|1011 2 00012958 1 7|c) terminates the calling thread
520|1011 2 00012958 1 8|d) makes value_ptr available to any successful
join with the
520|1011 2 00012958 1 9|terminating thread.
520|1011 2 00012958 1 10|Posix Ref: Component PTHREAD_EXIT
520|1011 2 00012958 1 11|Assertion 9945-1:1996 16.2.5.2-2(A)
520|1011 2 00012958 3 1|T2_cflag, expected 2, got 1
220|1011 2 1 11:09:43|FAIL