• TestingK42

Regression Tests

Within the K42-packages tree, there is a set of regression tests. To run, set K42_INITSCR to /home/regress/sysinit, or /home/regress-hw/sysinit when running on hardware. The latter will include the SDET benchmark.

Note: the regression tests require a set of users that are not in the default passwd and group files. Download from here:

• /etc/passwd

• /etc/group

If you place these files in the k42 config directory (~/k42-config) they will automatically be installed into the NFS root area when K42 is built.

We use the SDET benchmark to catch performance regressions. See a file called `Status' in the top directory of your K42 source for instructions on how to run it.

todo: how to control how many runs of the linux regression tests are done

todo: how to control number of cpus used for SDET and number of SDET runs etc.

LTP Tests

When running the LTP tests it appears to be necessary to set K42_NFS_ID to 0:0 (at least with the Australian setup)

Performance Tests

Christoph Lameter of SGI posted to the Linux IA64 kernel mailing list a small program intended to test page fault scalability. We have preliminary results of this program's performance on K42 posted at PftPerformanceK42.

We run the SDET benchmark nightly, and our performance history is shown on SdetPerformanceK42.

There are some procedures to follow when you are trying to get the highest performance out of K42 for a performance experiment. We summarize them in K42PerformanceExperiments.

System Call Coverage

Running /home/regress-hw/sysinit with TRACEPROC="" produces a trace of every system call invoked by SDET and regress. A uniqified list gathered on 2005-05-08 is in syscalls.txt.

Results

Just for reference, here are some recent SDET results:

ozlabs

All builds are noDeb.