From: Kern Sibbald Date: Wed, 25 Jun 2008 21:16:19 +0000 (+0000) Subject: Update ctest README X-Git-Tag: Release-3.0.0~1233 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=1aa23b20c12a20bbf4b95a5d9f25b7277d1801ef;p=bacula%2Fbacula Update ctest README git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@7232 91ce42f0-d328-0410-95d8-f526ca767f89 --- diff --git a/regress/README.ctest b/regress/README.ctest index 87361f58b4..bb2dfee206 100644 --- a/regress/README.ctest +++ b/regress/README.ctest @@ -51,6 +51,13 @@ So, you can choose between the following scripts: ./experimental-all # experimental disk and tape testing ./experimental-disk # experimental disk testing +We recommend that you start with the ./experimental-disk runs so that +you can check that everything is working fine. Once that is done, +try a nightly-xxx run. The difference is the experimental runs are just +that -- they are things where you are experimenting and it is expected that +something might be broken (bad ctest configuration, experimental source +code, ...), and nightly runs are not expected to fail. + If you are a developer and you have modified your local SVN repository, you should be running the experimental tests -- they are designed for developers. If you do modify your local repository and commit it, then run a nightly