|
|
Boost Testing : |
From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2007-11-20 11:01:05
Rene Rivera wrote:
> Markus Schöpflin wrote:
[...]
>> So, each run takes about 8 hours. That would mean that the next run should
>> have happened at 06:18 today. But now it's already 6 hours later, and still
>> the results from yesterday are showing.
>>
>> So what do these timestamps actually mean? The start of the report
>> generation cycle? Or the end of it? And is each cycle really taking 8
>> hours, or is the generation of the release branch results included here?
>
> This is just the trunk generation... And the times indicate the start of
> the run. So it would mean that the results might show up at
> current+2*delta.
So, taking into account delta=8h, at any given time I can expect that 16
hours later the results have been updated?
> Or another way, if you look at the results shortly
> after they are uploaded the date will be current+delta.
Not current-delta?
>> Also, the report generation machine shows a load average of 0.15/0.03/0.01,
>> which doesn't seem right to me if the reports are really regenerated
>> continuously.
>
> Hm, there's a rest period of five minutes between each run (to give me a
> chance to stop it and to OS updates as needed). But it's likely that the
> load is not high because two large chunk of time are taken up by steps
> that don't seem to take much CPU. Which would be generating the zip
> archive, and uploading it.
Markus