The GCC automated continuous testing system is, at present, a single machine which waits for a checkin to the GCC Subversion repository; checks out a URL of that tree; checks that it builds (for the native case, checks that it bootstraps); and runs the testsuite, checking whether any test which used to pass now fails.
The tester tests an i686-pc-linux-gnu native, running CentOS 5.x, with updated GMP, MPFR, and MPC.
The following information is available:
.sumfiles from the last time the tree successfully built for native;
If a build failure or a successful build with new regressions
occurs, the tester sends mail to the
mailing list. On any successful build, the tester also uses
test_summary script to send mail to the
If the tester is idle and the GCC tree has no regressions, the tester automatically tries to update its dejagnu and other tools daily:
At present, the tester does not send mail to individuals, only to mailing lists, but a previous version of the tester did do this and this feature is planned to be re-added in the future.