i386/sid results, updates to summaries, i386/ia64 diff

[Matt Taggart <taggart@debian.org>]

Hi debian-lsb,

1.) I have run the lsb-runtime-tests on i386 against unstable from 2003-10-16 
and using kernel-image-2.4.22-1-686-smp version 2.4.22-3 and posted the 
results on the webpage at,
   http://people.debian.org/~taggart/lsb/

2.) Like I did for ia64 I made a color-coded annotated summary,
   http://people.debian.org/~taggart/lsb/i386-20031016.tj.annotate.html
I have also updated the ia64 annotated summary,
   http://people.debian.org/~taggart/lsb/ia64-20030829.tj.annotate.html
A few things have turned green due to the waivers we filed and got INT/TSDs 
on.

3.) diff'ing the ia64 tj report and the i386 tj report reveals a few things,

Fail on ia64 but not i386
=========================
> /tset/LI18NUX2K.L1/base/fwide/T.fwide 4 FAIL
> /tset/LI18NUX2K.L1/base/vfprintf/T.vfprintf 5 FAIL

Unanalysed. These are glibc functions.

> /tset/LSB.os/files/dev_tty/T.dev_tty 1 UNRESOLVED

Unanalysed.

> /tset/LSB.os/mfiles/mmap_P/T.mmap_P 29 FAIL
> /tset/LSB.os/mfiles/mmap_P/T.mmap_P 34 FAIL
> /tset/LSB.os/mfiles/munmap_P/T.munmap_P 4 FAIL

Waiver/TSD (ia64 specific) PR#0022


Fail on i386 but not ia64
=========================
> /tset/POSIX.os/procenv/times/T.times 4 FAIL
> /tset/POSIX.os/procenv/times/T.times 6 UNINITIATED
> /tset/POSIX.os/procprim/fork/T.fork 5 UNRESOLVED

Unanalysed.

Fail on both(that we don't have waivers for)
============
> /tset/POSIX.os/devclass/c_iflag/T.c_iflag 6 FAIL
> /tset/POSIX.os/devclass/c_iflag/T.c_iflag 7 FAIL
> /tset/POSIX.os/devclass/c_iflag/T.c_iflag 8 FAIL
> /tset/POSIX.os/devclass/c_iflag/T.c_iflag 9 FAIL

Unanalysed.

> /tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 1 FAIL
> /tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 2 FAIL

Unanalysed. This is a glibc function. Did not fail in Jeff's
i386/woody and sarge testing. Jeff did you patch for this?

> /tset/POSIX.os/procenv/getlogin/T.getlogin 1 FAIL

This one is supposedly dependent on how the tests are run. In this case I
ssh'd into the system as vsx0 which is the recommended way to do it. I've
also tried running tests from a linux virtual console(should work) and
with `su - vsx0`(known to fail). This test needs some investigation.


Any help with the above would be appreciated. I think some libc6 bugs needs to 
be filed once we understand why the tests are failing.

Thanks,

-- 
Matt Taggart
taggart@debian.org