C P 2 K R E G R E S S I O N T E S T E R

## The automatic regression tester

### Goal

CP2K should be kept in good shape throughout its development. Bugs that are fixed should stay fixed, features that are working should remain in that state. In order to do so, automated testers downloads/builds/tests CP2K after every commit/every night. Correctness of results (parallel) and memory leak tests are reported.

### Info

Correctness runs are parallel runs using the g95 compiler with full error checking on a PC architecture. Even though we strive to reach the above goal, the rapid development of CP2K does imply that not all features are working or passing the high standard of Fortran conformance we require during this testing. Failing tests are an indication of possible problems, but as yet still quite common. Memory leak checking is performed using the free Fortran compiler g95 (www.g95.org). The up-to-date reference results for the parallel autotester can be downloaded from ftp://ftp.berlios.de/pub/cp2k/LAST.tar.gz, and the do_regtest script can be adapted to compare to these results. These reference results are not aimed to be used for porting/validating the code on different platforms. In this case you may easily expect to have several tests failing with a "WRONG RESULT" status. Anyway they can still be used to check if errors between the regtest and the reference are larger than a reasonable value (1.E-8 - 1.E-9), clearly identifying a problem with compiler or libraries.

### Autotester

The latest regtest report is available. as well as reports from 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 runs ago.
The latest memory leak report is available. as well as reports from 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 runs ago.

Back to the CP2K homepage