Minutes of the June 21 teleconference
Andrew Josey <[email protected]>
| Newsgroups | gmane.linux.lsb.test-suite |
|---|---|
| Message-ID | <[email protected]> |
All
Enclosed are my notes from this weeks teleconference.
regards
Andrew
-----
LSB Test Teleconference June 21 2005
Andrew Josey
Gordon McFadden
Mats Wichmann
Stew Benedict
Thorsten Kukuk
Marvin Heffler
Apologies
Stuart Anderson
1. Review the minutes of the last meeting,
No comments on the minutes from the last meeting
2. Preparing test release candidates for LSB 3.0 certification
As per the last call we continue to focus on preparing the
test components for LSB 3.0 certification launch:
LSB Runtime:
TET harness package -- rc candidate
This was rebuilt after checking with the application test tools
lsb-runtime -- release candidate now available
Some problems seen:
sigconcept.42
fork.5 timing
however not major enough to require a rebuild. We can handle
small numbers of problems thru the certification problem reporting
process
lsb-vsw4 -- release candidate now available
lsb-c++ -- release candidate
results look good, just one failure
currently a TSD,
http://www.opengroup.org:8000/lsb/publicpr/PRView?PR=0065
We would reissue this against the new version of the test suite
when we go live for certification
lsblibchk-- release candidate available
some problems remaining... with missing symbols
bug 814 , can lead to a significant number of errors (60 or 80 errors)
a must fix for GA
lsbcmdchk-- release candidate available
LSB Application:
lsbappchk-- release candidate available
lsbarchk-- release candidate available
lsbpkgchk-- release candidate available
3. wip (initd, lsb-xts5)
Tests for initd (install_initd, remove_initd, key files,
directories ) are under development in the wip directory
of the cvs tree. initd needs more testing, we plan to extend the testset
to be an LSB.misc so we can add further tests. This will
require a restructure under the wip directory
A set of tarballs to run the initd tests are available
at https://www.opengroup.org/infosrv/lsb/tmp/
Download all the files, and then as root run
sh install.sh
Rui has prepared an initial cut of lsb-xts5 (the X test suite
from X.Org). This uses an approach to check out the sources
from X.Org rather than retaining the full source tree.
We need volunteers to try this out,
its obtainable at
http://cvs.gforge.freestandards.org/cgi-bin/cvsweb.cgi/tests/lsb-xts5/?cvsroot=lsb
The README for lsb-xts5 follows:
-----start README---
This is a version of the XTS5 test suite which has been modified for
use as part of the LSB compliance testing.
Notice: lsb-xts5 needs tet3 package to be installed before being built.
Please download lsb-tet3-lite and lsb-tet3-lite-devel from
ftp://ftp.freestandards.org/pub/lsb/test_suites/beta/binary/runtime/
and install them at first before trying to build lsb-xts5.
Building
--------
Checkout the source code of xts5 from cvs.freedesktop.org into current
directory. Currently, lsb-xts5 is based on xts5.1.5 (which is derived
from vsw5.1.5). So you can checkout the source code of xts5 by the
following way:
export CVSROOT=:pserver:[email protected]:/cvs/xtest
cvs -z9 checkout -r vsw5_1_5 xts5
and then build it by executing the following command:
./build.sh
Executing the test suites
-------------------------
./run_xts5.sh
Packaging
---------
cd package; make
-----end README---
4. bugzilla review.
The key bugs for test are below,
we should ensure that the dependency is set accordingly.
LSB 3 runtime (platform) tests:
http://bugs.linuxbase.org/show_bug.cgi?id=612
Blocking bugs: 4, 405, 591, 771, 814, 843, 979, 981, 1006
LSB 3 application tests:
http://bugs.linuxbase.org/show_bug.cgi?id=613
Blocking bugs: 619, 620, 724, 735, 805, 822, 880, 984, 986,
997, 999, 1001, 1003
We will review the bugzilla next tuesday. We need to resolve
all blocking bugs. We need to consider that if a bug is
not a critical issue that it can always be addressed
for certification through the problem reporting system.
Next Steps:
The current plan is to final closeout and approval of test
suite releases for the certification launch. We need to ensure
an approved version of each test tool is ready for July 1.
Next meeting:
*Note the time shift to allow a longer meeting*
Tues Jun 28 3:30 UK, 07:30 Pacific, 09:30 Austin.
The call will last 1 hour