0N/ACopyright (C) 2000 Internet Software Consortium.
0N/A$Id: tests,v 1.10 2000/11/14 17:58:44 gson Exp $
0N/AWe do hourly test builds of the bind9 tree. This is an attempt to
0N/AThe scripts driving the build system are in ~
wpk/b9t. They are now
0N/Athat this is a separate repository from the bind9 one). The builds
0N/Aare driven by cron jobs separately installed on each build system,
0N/AThe sources are checked out, and the web reports are generated,
0N/Aon bb, as driven by the following cron jobs:
2362N/A # Check out the current bind 9 version and make the source tarball.
0N/A # run the bind 9 build status report generator
0N/AEach host has a separate crontab entry for building the server and
0N/Arunning tests. Here are examples from bb and sol:
0N/A # build the BSD-3.1 version of bind 9
0N/A # bind 9 build for Solaris 5.6
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
: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
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
The output from the make process is in
The output from the later stages of the process is under
harder to find (?), they have names starting with a period:
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.
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 file
The failed file itself contains an exit code, which is not particularly
useful. The more useful information is in the various log files under