The nightly regression testing system consists of several shell scripts
and some perl scripts. The goal is to check out a fresh tree, run "make check" on it,
record the results and summarize the results to the team and to the web site.
Output can be found on adams,
although the tests are actually run on another project machine.
The best way to do nightly testing is to setup a new account. We call the
account "build" - you could call it something else, but there may
still be some references to ~build in the scripts.
Files you need to know about
As few files as possible need to be extracted from the source tree -
files are run from the source tree whenever possible. However, there
are some bootstrap and configuration files that are necessary.
There are 7 files in testing/utils that are involved:
- This is the root of the build process. This file should be copied out
of the CVS tree, to $HOME/bin/nightly.sh of the build account. This
file should be invoked from cron.
- This file should be copied to $HOME/freeswan-regress-env.sh. It
should be edited to localize the values. See below.
- This file needs to be copied to $HOME/bin/regress-cleanup.pl. It
is invoked by the nightly file before doing anything else. It
removes previous nights builds in order to free up disk space for
the build about to be done.
- A script used to send results email to the "team". This sample
script could be copied to $HOME/bin/teammail.sh. This version will
PGP encrypt all the output to the team members. If this script is used,
then PGP will have to be properly setup to have the right keys.
- This is the first stage of the nightly build. This stage will
call other scripts as appropriate, and will extract the source code
from CVS. This script should be copied to $HOME/bin/regress-nightly.sh
- This is the second stage of the nightly build. It is called in
place. It essentially sets up the UML setup in umlsetup.sh, and
calls "make check".
- This script will summarize the results from the tests to a
permanent directory set by $REGRESSRESULTS. It is invoked from the
stage2 nightly script.
- This script is called at the end of the build process, and will
summarize each night's results (as saved into $REGRESSRESULTS by
regress-summarize-results.pl) as a chart using gnuplot. Note that
this requires at least gnuplot 3.7.2.
For more info on KERNPOOL, UMLPATCH, BASICROOT and SHAREDIR, see
User-Mode-Linux testing guide.
- Extract copy of some kernel source to be used for UML builds
- matching User-Mode-Linux patch.
- the root file system image (see
User-Mode-Linux testing guide).
- The /usr/share to use.
- A directory in which to store the nightly regression
results. Directories will be created by date in this tree.
- The path to the tcpdump
to use. This must have crypto compiled in, and must be at least 3.7.1
- An extracted copy of the RedHat 7.2. kernel source. If set, then
the packaging/rpm-rh72-install-01 test will be run, and an RPM will
be built as a test.
- An extracted copy of the RedHat 7.3. kernel source. If set, then
the packaging/rpm-rh73-install-01 test will be run, and an RPM will
be built as a test.
- The list of people who should receive nightly output. This is
used by teammail.sh
- How many lines of failed test output to include in the nightly
- PATH=$PATH:/sandel/bin export PATH
- You can also override the path if necessary here.
- The CVSROOT to use. This example may work for anonymous CVS, but
will be 12 hours behind the primary, and is still experimental
- For the release tools, where to put the generated per-snapshot
- the name of the last release branch (to find the right