3500N/AWe do hourly test builds of the bind9 tree. This is an attempt to
3500N/AThe scripts driving the build system are in ~
wpk/b9t. They are not
3500N/Aunder CVS control. The builds are driven by cron jobs separately
3500N/Ainstalled on each build system, running as user wpk. Here is a
3500N/AThe sources are checked out, and the web reports are generated,
3500N/Aon bb, as driven by the following cron jobs:
3500N/A # check out the current bind 9 version and make the source tarball
3500N/A # run the bind 9 build status report generator
3500N/AEach host has a separate crontab entry for building the server and
3500N/Arunning tests. Here are examples from bb and sol:
3500N/A # build the BSD-3.1 version of bind 9
3817N/A # bind 9 build for Solaris 5.6
3500N/AThe actual builds take place in a directory whose location differs
3500N/Aamong systems. On most of them, it's on a local disk, under /build.
3500N/AOn some, it's on NFS; in this case the location is defined in
3500N/ATo make things more confusing, "sol" also builds an extra
3500N/Acopy of bind9 using gcc, even though it is not shown
3500N/A # bind 8 build for Solaris 5.6-gcc
The output from the various stages is under
To make the files 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.