INSTALLING AND RUNNING THE VSX4 TEST SUITE ------------------------------------------ Please ensure that you have read INSTALL.SETUP before performing the instructions listed here. WARNING for 2.4test kernels ---------------------------- If you are running the test suite on a 2.4test kernel you may encounter a kernel lock up and filesystem corruption. This has been verified on 2.4test-1 and 2.4test-2 kernels. Later kernels may have this problem fixed. You've been warned. Dependencies for VSX4 --------------------- The vsx4 tests require yacc to be installed (bison will not work, but byacc version 1.9 will). Some distributions (such as Debian) symlink yacc to bison by default. In this case you will have to install byacc separately and ensure that it is the yacc used by the user vsx0 by default (a source rpm of byacc is included in the LSB.tools directory). This should be done prior to configuring and installing either the lsb-fhs or vsx4 test suites. The vsx4 test suite requires the glibc locale data to be installed. With some distributions such as Redhat this is included in the standard glibc rpm, whereas with Debian it is an optional extra package (i18ndata). The test suite requires additional users and groups to be setup. The script /home/tet/tests/LSB.tools/uids.setup will setup the correct configuration if this has not already been done. Configuring, Installing and Running the test suite -------------------------------------------------- Configure and install the vsx4 test suite You should already be logged in as the vsx0 user. Switch to the /home/tet/tests/vsx4 directory $ cd /home/tet/tests/vsx4 Dot in the lsb-fhs /home/tet/tests/vsx4 profile $ . ./profile Run the install_wrapper script which will lead you through the configuration of the tests: $ sh install_wrapper.sh The test will want to work with a disk partition. You can alternatively use a loopbacked ext2 filesystem. The script will prompt you appropriately. Note that to successfully use a loopback filesystem you must have the loopback option compiled into your kernel (this is true for most configurations). You can also choose a partition on a hard drive that you want to use (don't specify a partition with any useful data on it), or you can specify a floppy drive. In both cases you don't want to mount the partition/floppy, but you do want to have the floppy in the drive if you chose to use a floppy. Using the floppy drive will make the tests run slower. The script will then install and run the tests. You will be shown a summary of the results of tests and be given the option of re-running only the tests that failed. Note that you can expect the tests to take approximately 6-8 hours to run (on a 400Mhz PII system). $ vrpt results/XXXXe/journal After the tests have been installed and run for the first time they can all be re-run at a later time by using the following command: $ tcce -p To run specific tests: $ tcce -y games -p # games tests $ tcce -y /var/ -p # those matching /var/ only A journal file will be created each time and can also be formatted using the vrpt command. Expected Failures ----------------- A summary of failures encountered whilst running the tests on a Debian (woody) system using a 2.2.15 kernel is in FAILURES.VSX4. There are differences in failures between kernel versions especially between 2.2 and 2.3, but even between stable versions as well. For ease of use the test suite has been configured to use pseudo terminals. Pseudo terminals are unable to emulate some features of the real terminal interfaces and so you can expect the following tests to fail: /tset/POSIX.os/devclass/tcdrain/T.tcdrain 2 Posix Ref: Component TCDRAIN Assertion 7.2.2.2-05(C) /tset/POSIX.os/procprim/sigconcept/T.sigconcept 35 Posix Ref: Component Signal Concepts Assertion 3.3.1.4-48(C) Component Signal Concepts Assertion 3.3.1.4-49(C:D) /tset/POSIX.os/devclass/i_close/T.i_close 1 Posix Ref: Component Terminal Interface Assertion 7.1.1.11-70(C) /tset/POSIX.os/devclass/i_spchars/T.i_spchars 1 Posix Ref: Component Terminal Interface Assertion 7.1.1.9-47(C) /tset/POSIX.os/devclass/i_spchars/T.i_spchars 3 Posix Ref: Component Terminal Interface Assertion 7.1.1.9-49(C) /tset/POSIX.os/devclass/i_spchars/T.i_spchars 5 Posix Ref: Component Terminal Interface Assertion 7.1.1.9-51(C) /tset/POSIX.os/devclass/i_spchars/T.i_spchars 14 Posix Ref: Component Settable Parameters Assertion 7.1.2.2-28(C) Posix Ref: Component Settable Parameters Assertion 7.1.2.2-29(C) /tset/POSIX.os/devclass/i_spchars/T.i_spchars 17 Posix Ref: Component Terminal Interface Assertion 7.1.1.9-62(C) /tset/POSIX.os/devclass/tcdrain/T.tcdrain 7 /tset/POSIX.os/devclass/tcflow/T.tcflow 2 Posix Ref: Component TCFLOW Assertion 7.2.2.2-05(C) /tset/POSIX.os/devclass/tcflow/T.tcflow 6 Posix Ref: Component TCFLOW Assertion 7.2.2.2-09(C) /tset/POSIX.os/devclass/tcflow/T.tcflow 7 Posix Ref: Component TCFLOW Assertion 7.2.2.2-10(C) /tset/POSIX.os/devclass/tcflow/T.tcflow 8 Posix Ref: Component TCFLOW Assertion 7.2.2.2-11(C) /tset/POSIX.os/devclass/tcflow/T.tcflow 13 Posix Ref: Component TCFLOW Assertion 7.2.2.2-X2(C) /tset/POSIX.os/devclass/tcflow/T.tcflow 14 Posix Ref: Component TCFLOW Assertion 7.2.2.2-X3(C) /tset/POSIX.os/devclass/tcflow/T.tcflow 15 Posix Ref: Component TCFLOW Assertion 7.2.2.2-X4(C) /tset/POSIX.os/devclass/tcflow/T.tcflow 16 Posix Ref: Component TCFLOW Assertion 7.2.2.2-X5(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 1 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-05(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 2 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-06(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 3 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-07(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 4 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-08(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 5 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-09(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 6 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-10(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 10 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-X5(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 11 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-X2(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 12 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-X3(C) /tset/POSIX.os/devclass/tcflush/T.tcflush 13 Posix Ref: Component TCFLUSH Assertion 7.2.2.2-X4(C) /tset/POSIX.os/devclass/tcsetattr/T.tcsetattr 1 Posix Ref: Component TCSETATTR Assertion 7.2.1.2-05(C) /tset/POSIX.os/devclass/tcsetattr/T.tcsetattr 13 Posix Ref: Component TCSETATTR Assertion 7.2.2.2-X1(C) /tset/POSIX.os/files/creat/T.creat 11 Posix Ref: Component CREAT Assertion 5.3.2.2-39(A) /tset/POSIX.os/files/open/T.open 16 Posix Ref: Component OPEN Assertion 5.3.1.2-50(A) /tset/POSIX.os/procprim/sigconcept/T.sigconcept 30 Posix Ref: Component Signal Concepts Assertion 3.3.1.3-38(A) Posix Ref: Component Signal Concepts Assertion 3.3.1.3-39(A:B) /tset/POSIX.os/procprim/sigconcept/T.sigconcept 31 Posix Ref: Component Signal Concepts Assertion 3.3.1.4-42(A) /tset/POSIX.os/procprim/sigconcept/T.sigconcept 34 Posix Ref: Component Signal Concepts Assertion 3.3.1.4-45(C) Posix Ref: Component Signal Concepts Assertion 3.3.1.4-46(C:D) /tset/POSIX.os/procprim/sigconcept/T.sigconcept 36 Posix Ref: Component Signal Concepts Assertion 3.3.1.4-51(A) Posix Ref: Component Signal Concepts Assertion 3.3.1.4-52(A:B) /tset/POSIX.os/procprim/sigconcept/T.sigconcept 37 Posix Ref: Component Signal Concepts Assertion 3.3.1.4-53(A) Posix Ref: Component Signal Concepts Assertion 3.3.1.4-54(A:B) You can also run the test suite using a null modem cable and two serial ports instead of the pseudo terminals. You will also need to make changes in the `Terminal Interface Parameters' part of vsx4/TESTROOT/tetexec.cfg to configure the test suite to use a null modem cable. When this is done you should expect all of the above tests to pass.