From 3aef3c456b4dbc71008c8ffe3b9d0d2f025c2888 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Thu, 13 Mar 2008 21:06:36 +0000 Subject: [PATCH] Add Frank's explanation for ctest backing out changes git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@6607 91ce42f0-d328-0410-95d8-f526ca767f89 --- regress/README.ctest | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/regress/README.ctest b/regress/README.ctest index 9b8986ad8e..34543663bc 100644 --- a/regress/README.ctest +++ b/regress/README.ctest @@ -165,3 +165,30 @@ BuildName parameter was misnamed, and intended to be treated more as a build platform name, rather than the name of the build being tested. Rather than create a hook to tag the version being tested, everyone as far as I can tell just seems to rely on the timestamp of the test. +====== + +NOTE !!!!!!!!! ctest can actually back out changes that have been made to +your local source repository. As a consequence, it is probably better not to +use a directory in which you are developing code for Nightly tests. Seee the +below explanation given by Frank Sweetser. + +When a Nightly run is done, the timestamp is set to the last occurring +instance of the time defined by the NightlyStartTime parameter. The piece +that I missed is that, in addition to using that timestamp for reporting to +the dashboard, the update stage also uses that point in time to determine +exactly which version of the repository to check out. + +So if you make commit changes at 10PM EST, and then run a Nightly test run, +the NightlyStartTime of 9PM EST will back out those changes in the local +repository. Any subsequent runs that are started at 9PM EST the following day +or later will include them. This implies to me that NightlyStartTime should +be set such that you don't expect any developers to commit any changes in +between NightlyStartTime and the time at which the ctest run actually starts. + +The alternative is to make use of the Experimental track. While it normally +just uses the local source tree as is, you can manually have it update: + +ctest -D ExperimentalUpdate + +Unlike Nightly, this will update to whatever the latest version of the +repository is. -- 2.39.5