[CMake] Strange behavior with Nightly builds
norulez at me.com
norulez at me.com
Fri Jul 27 17:58:40 EDT 2012
Hello Richard,
hello David,
sorry for the long response time, I tried to get it working but it doesn't work.
I'm trying to describe it in a more detail:
1.) CTestScript.cmake is now configured with set(CTEST_NIGHTLY_START_TIME "3:00:00 UTC")
2.) the windows slave is configured as GMT+2 in the scheduler at every minute (continuous) between 6am and 10pm and nightly at 1 am (UTC-2 for europe, which is described at http://www.kitware.com/blog/home/post/77)
3.) the last revision at 4pm (2012-07-01) is for e.g. 80.
4.) the nightly build at 1am (2012-07-02) removes all files in the build directory and update/configure the project.
At this point the revision should be 80 because it is the last commit of the previous day (at 4 pm, but could also be 6pm or 7pm on 2012-07-01) => HEAD (for 2012-07-01)
!!!!! And here is the problem, the revision which is checked out isn't 80, it is a revision before 80 (e.g. 79, 75, ...)
5.) Continuous build for a developer commit on 2012-07-02 at 6 am with revision 81
step 5 is the expected result, but the real thing is, that the Continous build at 6am is done without a developer commit (for revision 80) because of the failed nightly build (commit was < 80).
Much thanks in advance
Best Regards
Am 22.06.2012 um 14:14 schrieb Richard Wackerbarth <richard at NFSNet.org>:
> I made a minor error in my previous posting. I forgot the first run as continuous starts up on the second day.
> I have make the correction inline below.
>
> On Jun 22, 2012, at 2:09 AM, NoRulez wrote:
>
>> Hello Richard,
>>
>> >> What is the configured cutoff time for Nightly runs?
>> Did you mean the nightly build time?
>
> I mean this value (for example in CTestConfig.cmake)
> such as:
>
> set(CTEST_NIGHTLY_START_TIME "21:00:00 EDT")
> or
> set(CTEST_NIGHTLY_START_TIME "1:00:00 UTC")
>
> But let's be certain that we both are talking about the consistent times, namely UTC.
>
>> >> During which hours does the "continuous" builder run?
>> Between 6 am and 10 pm
> (UTC ?)
>
> (Note A) See below
>
>> >> When does the "nightly" builder run?
>> Nightly build time is configured for 23:00 UTC (11 pm)
>>
>> >> Which builds do you expect to be posted to "continuous"?
>> At 10 pm and at 6 pm in the morning (next day) the commit should be e.g. 48
>
> I interpret (Note A) to indicate that you should expect the following runs:
> 5, 6, 7, ... , 21, 29 - 45, 53 - 69, etc.
> Commit 5 is processed when the builder restarts at 6 AM.
> Commit 6 is processed shortly after 6:15 AM
> The builder shuts down for the night before Commit 22 is posted at 10:15 PM
>
>> >> Which builds do you expect to be posted to "nightly"?
>> At 11 pm the commit should be e.g. 48 (HEAD revision) which means the last commit from the current day
>
> At 11 PM, the last commit was the one made at 10:15 PM, namely 22, 46, 70, ...
>
>> e.g.: If the last commit from the 21.06.2012 is at 12:30 am
>
> I don't know how you expect 12:30 AM to be the last commit of the day. The day started only 30 minutes earlier.
>
>> and has the commit 32, then the nightly build from the 21.06.2012 at 23:00 (11 pm) has (should have) the commit 32 too.
>
> This doesn't make sense. (And please follow my assumptions -- all of the commits in my scenario occur at 15 minutes past the hour. There are no commits made at 12:30 am)
>
> Please draw your timeline, mark all of the actions and revise your expectations.
>
>> The only difference is that the nightly builds starts from an empty build directory (the directory content are removed).
>
> A typical distinction.
>
>> Thanks in advance
>>
>> Best Regards
>>
>>
>> Am 21. Jun 2012 um 20:20 schrieb Richard Wackerbarth <richard at NFSNet.org>:
>>
>>> From reading this, I get the distinct impression that your are not interpreting the meaning of "nightly" in the same way that the rest of us are doing so.
>>>
>>> Let's assume the following:
>>>
>>> At 15 minutes past each hour, a new commit is added to the repository.
>>>
>>> For the sake of description, the "zeroth" commit happens at 12:15 AM on June 21
>>> Commit #1 is at 1:15 AM,
>>> ...
>>> Commit #18 is at 6:15 PM,
>>> ...
>>> Commit #22 is at 10:15 PM,
>>> Commit #23 is at 11:15 PM,
>>> Commit #24 is at 12:15 AM on June 22
>>> ...
>>> Commit #47 is at 11:15 PM,
>>> Commit #48 is at 12:15 AM on June 23
>>> ...
>>>
>>> etc.
>>>
>>> Further, assume that a build requires 5 minutes to run.
>>>
>>> ===
>>>
>>> Now it terms of those assumptions,
>>> please tell me:
>>>
>>> What is the configured cutoff time for Nightly runs?
>>> During which hours does the "continuous" builder run?
>>> When does the "nightly" builder run?
>>>
>>> Which builds do you expect to be posted to "continuous"?
>>> Which builds do you expect to be posted to "nightly"?
>>>
>>> ===
>>>
>>> With those answers, perhaps I will be able to understand what you expect and help explain how you might achieve it.
>>>
>>> Richard
>>>
>>> On Jun 21, 2012, at 1:29 AM, NoRulez wrote:
>>>
>>> > Has no one an idea on how to do so or is such functionality missing?
>>> >
>>> > Thanks in advance
>>> >
>>> > Best Regards
>>> >
>>> >
>>> > Am 15. Jun 2012 um 08:38 schrieb NoRulez <norulez at me.com>:
>>> >
>>> >> Hello David,
>>> >>
>>> >> but the problem is, that the timestamp is one day behind, so this doesn't work and I get previous revisions. (Our nightly build starts at 23:00 and not at 1 am)
>>> >> However is there a way to update to the HEAD revision?
>>> >>
>>>> >> Best Regards
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120727/8fb2ec43/attachment-0001.htm>
More information about the CMake
mailing list