GCC Automated Testing System

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 a powerpc-darwin9.8 native. The system has GMP 4.2.4 and MPFR 2.3.2 installed in /usr/local.

The following information is available:

• current status of the tester also available as a continuously updated JavaScript version;
• logfile containing the results of each test;
• log output of the last build for native;
• .log and .sum files from the last time the tree successfully built for native;
• The list of regressions (tests that used to pass and now fail) from the last time the tree successfully built for native;
• list of tests that are known to pass, for native.

If a build failure or a successful build with new regressions occurs, the tester sends mail to the gcc-regression mailing list. On any successful build, the tester also uses the test_summary script to send mail to the gcc-testresults mailing list.

If the tester is idle and the GCC tree has no regressions, the tester automatically tries to update its dejagnu and other tools daily:

• current status;
• logfile;
• log output of the last build;

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.