a3128c1995310262648e575a9ff148d5741fd167Tinderbox UserCopyright (C) 2000 Internet Software Consortium.

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark AndrewsSee COPYRIGHT in the source root or http://isc.org/copyright.html for terms.

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrews

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrews$Id: tests,v 1.11 2000/11/27 19:52:16 gson Exp $

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrews

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark AndrewsWe do hourly test builds of the bind9 tree. This is an attempt to

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrewsdocument how they work.

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrews

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrews

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrews* How things work

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrews

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark AndrewsThe scripts driving the build system are in ~wpk/b9t. They are now

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrewsunder CVS control; the repository is in rc:/proj/cvs/isc/b9t (note

bf8267aa453e5d2a735ed732a043b77a0b355b20Mark Andrewsthat this is a separate repository from the bind9 one). The builds

dcc6bde0a3c6580514675c59f8ffa499cee8f7c5Brian Wellingtonare driven by cron jobs separately installed on each build system,

a1e2170ad5c5018fbe8f7b8449d8885d5d298e88Mark Andrewsrunning as user wpk.

dcc6bde0a3c6580514675c59f8ffa499cee8f7c5Brian Wellington

dcc6bde0a3c6580514675c59f8ffa499cee8f7c5Brian WellingtonThe sources are checked out, and the web reports are generated,

dcc6bde0a3c6580514675c59f8ffa499cee8f7c5Brian Wellingtonon bb, as driven by the following cron jobs:

dcc6bde0a3c6580514675c59f8ffa499cee8f7c5Brian Wellington

dcc6bde0a3c6580514675c59f8ffa499cee8f7c5Brian Wellington # Check out the current bind 9 version and make the source tarball.

a1e2170ad5c5018fbe8f7b8449d8885d5d298e88Mark Andrews # Argument to maketar.sh should be v9_0 for 9.0 release branch,

47d837a49967a6a1b290024f5efb0669276013b1Mukund Sivaraman # HEAD for mainline.

45 2-22 * * * PLATFORM=BSD-3.1 && . $HOME/b9t/hosts/$PLATFORM/env && \

nice sh $HOME/b9t/bin/maketar.sh HEAD \

>/proj/build-reports/bind9/tarsrc.txt 2>&1

#

# run the bind 9 build status report generator

#

30 3-22 * * * perl $HOME/b9t/bin/b9status.pl \

> /proj/build-reports/bind9/bind9.html 2> /dev/null

Each host has a separate crontab entry for building the server and

running tests. Here are examples from bb and sol:

#

# build the BSD-3.1 version of bind 9

#

0 3-22 * * * $HOME/b9t/bin/b9t.cron BSD-3.1

#

# bind 9 build for Solaris 5.6

#

0 3-22 * * * $HOME/b9t/bin/b9t.cron SunOS-5.6

Do not confuse the shell script ~wpk/b9t/bin/b9t.cron with the crontab

template (?) ~wpk/b9t/b9t.cron. Although they have the same name,

they are not related.

The shell script b9t.cron then calls make, using the makefile b9t.mk

in the same location. This makefile moves the old status files out of

the way and runs through the tests.

The current test schedule is as follows:

:45 CVS tree extracted, tarball built and distributed

:00 Most tests begin

:45 Status report generator runs (was :30)

aix: I can't seem to access that machine; it appears to be down.

bb: Build starts at top of hour, 0300 to 2200

durango: Build starts at top of hour, 0300 to 2200

trantor: Build starts at top of hour, 0300 to 2100, odd-numbered hours

only

hp: Build starts at top of hour, 0300 to 2200

irix: Build starts at top of hour, 0300 to 2200

netbsd: Build starts at top of hour, 0300 to 2200 (was :45)

aa: Build starts at top of hour, 0300 to 2200

rc: Build starts at top of hour, 0300 to 2200

mirepoix: Build starts at top of hour, 0300 to 2200

sol: Build starts at top of hour, 0300 to 2200

truffle: Build starts at top of hour, 0300 to 2200

anthrax: Build starts at top of hour, 0300 to 2200

The actual builds take place in a directory whose location differs

among systems. On most of them, it's on a local disk, under /build.

On some, it's on NFS; in this case the location is defined in

~wpk/b9t/hosts/$PLATFORM/env.

The output from the make process is in

~wpk/b9t/hosts/$PLATFORM/b9t-status, and the output from

The output from the later stages of the process is under

/proj/build-reports/bind9/hosts/$PLATFORM. To make the files

harder to find (?), they have names starting with a period:

.populate

.config

.build

.test

* Common problems

Sometime named processes fail to die when the tests are done,

interfering with the next test. Just kill them.

On hp.rc.vix.com, the tests often fail because of NFS I/O errors.

When this happens, the machine needs to be rebooted. It will not

come up again without manually entering commands on the console.

On bb, the tests sometimes fail because .nfs* files stuck in the build

tree keep it from being completely deleted when the next test runs.

The .nfs* files cannot be deleted, but they can be moved, so one way

of fixing this is to move them to ~wpk.

* Failure locking

When a test fails, further testing on that host is disabled in order

to preserve evidence. To remove the lockout and allow more tests to

be run, log in to bb, su, su wpk, and remove the "failed" files:

rm /proj/build-reports/bind9/hosts/*/failed

The failed file itself contains an exit code, which is not particularly

useful. The more useful information is in the various log files under

the build report.