1) Checks which packages have been modified in the last 24 hours
2) Uses glastpack.pl to do a recursive checkout of the heads of the packages listed in part 1) (all into the same area or "vat")
3) Tries to build, then run the tests for these packages (note: it looks for test programs using the name convention test_"package_name".exe; currently only tests with that name are run)
The rationale for the above method is that packages are usually modified in groups so that it is often the case that changes in a package that is at the head depend on changes in another package that is currently at the head. This method can also lead to problems when incompatible changes are in fact at the head of a dependant package - some choices had to be made... A set of web pages containing the results of the nightly build, Monday.htm ... Sunday.htm with tables summarizing the weeks nightly build results, is generated and cycled through. To view the latest results see:
Users can also generate builds and tests of individual or checkout packages (and are emailed the URL of the test results). To view a directory of build and test outputs (generted both by users and the automated facilities) see:
K.Young Last Modified: