The Pencil Code

Automatic tests

To ensure reproducability, the Pencil Code is tested for a number of sample applications. This is important for us in order to make sure certain improvements in some parts of the code do not affect the functionality of other parts. For other users who suspect that a new problem has emerged it could be useful to first see whether this problem also shows up in our own tests. The latest test results for a can be seen online:

level	name	description	time	OK	runs	host	compiler	maintainer
0	minimal	no- & most-modules	minutely		latest (previous)	pencil-code.org	GNU 9.4	Philippe
0+1	basic	same as Travis	minutely		latest (previous)	Norlx51	GNU 13.3	Axel/Philippe
2	normal	without basic	*/*:15		latest (previous)	Norlx51	GNU 13.3	Axel/Philippe
0-2	default	basic + normal	*/2:03		latest (previous)	Norlx65	GNU 13.3	Philippe/Axel
3	extended	without default	*/*:55		latest (previous)	Norlx51	GNU 13.3	Axel/Philippe
0-3	full test	default + extended	*/6:31		latest (previous)	pencil-code.org	GNU 9.4	Philippe
4	fixme	succeeded before	*/6:45		latest (previous)	Norlx51	GNU 13.3	Axel/Philippe
5	overlong	runs less often	15:31		latest (previous)	Norlx65	GNU 13.3	Philippe/Axel
6-9	defective	known to fail	03:31		latest (previous)	Norlx65	GNU 13.3	Philippe/Axel

Legend: */* means every hour, */6:31 means 31 minutes after full hours divisible by 6.
Status of auto-tests: scheduled; running; failed; succeeded.
Tests are triggered only if there are new updates to the code.

Other tests

• basic test (levels 0+1) Travis minutely (latest checkin job log)

Test your changes

Note: before checking in your own changes, you should at least do the very minimal auto-tests:

You may alternatively choose the desired test levels, e.g. '--level=0+1' to run the "basic" auto-test set or '--max-level=3' for the "full" test.