Back to developer page.
We use Buildbot for automated building and testing of Fast Downward. The Buildbot master for Fast Downward is located at http://buildbot.fast-downward.org/. We recommend running ./misc/run-all-tests locally before pushing to the master repository, to catch style and compilation errors (on the same operating system) early. This script can also help you to fix any errors the Buildbot found in your code.
The setup is documented in the DMI wiki (only accessible from the Uni Basel network).
Our Buildbot uses eight workers with different operating systems, compilers, and LP solvers:
- Ubuntu 64-bit 16.04, GCC 5.4, CPLEX 12.8
- Ubuntu 64-bit 16.04, GCC 5.4, no LP solver
- Ubuntu 64-bit 18.04, GCC 8.2, CPLEX 12.8 (We call this worker the foreman and use it for builds that only need to run on a single worker)
- Ubuntu 64-bit 18.04, GCC 8.2, no LP solver
- Ubuntu 64-bit 18.04, clang 3.9, CPLEX 12.8
- Ubuntu 64-bit 18.04, clang 3.9, no LP solver
- Ubuntu 32-bit 18.04, GCC 8.2, no LP solver
- Windows 7 64-bit, VS 2017, CPLEX 12.8
macOS Sierra 64-bit, AppleClang 8.0.0, no LP solver
On every commit on the default branch, we run the following tests
- A style check of the code (only on the foreman). If these tests fail, the others are not run.
- Build tests on all workers. These are slightly different for the different operating systems
- All Linux workers
We test an incremental build of the release configuration, followed by clean builds of the release and debug configurations. We then run all our code tests.
- Autodoc: if the builds on all Linux workers are successful, we also update our documentation in this wiki. This is run only on the foreman.
Similar to the Linux setup, we start with in incremental build of the configuration releasenolp (ignoring the installed LP solver) followed by clean builds of releasenolp and debugnolp. We then test clean builds of release and debug, that use an LP solver. We do not run any code tests on Windows.
We test an incremental build of the release configuration, followed by clean builds of the configurations release and debug. We then run exit code tests and test some benchmark tasks. We do not include translator tests as on Linux, because we don't have a running Python3 installation.
- All Linux workers
In addition to the tests that run on every commit, we run a nightly and a weekly test, that both run some default configurations on the first problem of Gripper and Miconic to check for any performance regressions. We also have a builder that can only be triggered manually and recreates the baseline for these nightly/weekly tests.