Right now the default runtime string in XmlData is set to "runtime".  If we want to make it a convention to have "runTime" as the default runtime string I can change it.

Cheers,
austen

On 4/11/06, Julie Ann Sakuda <[EMAIL PROTECTED]> wrote:
Is there supposed to be a runTime for build data?  I didn't see it in
the docbook.  The XmlData sensor automatically created the runtime
attribute for me.

I will change the tool name to something other than Ant.  Can you just
delete that data?  Is there anyway to get rid of these emails from the
archive?  I realize now I accidently had it send to public server.  I
have a feeling that I'm NOT supposed to have the first line of data
listed below publicized to this entire list...

~Julie

(Cedric) Qin ZHANG wrote:

> Hi, Julie,
>
> I just realized that you are writing a new build sensor for Aaron by
> parsing cruisecontrol log file. There are two suggestions:
> (1) Change "runtime" to "runTime".
> (2) Chang tool name to something other than "Ant".
>
> Thanks.
>
> Cedric
>
>
> (Cedric) Qin ZHANG wrote:
>
>> Thanks to Hongbing's effort, we find something very weird:
>>
>> In Julie April 10's build data, there are two entries:
>> ----
>>      Success         Ant     ----    04/10/2006-16:58:22     {projectName=????,
>> runtime=1144724287789, buildDate=1129839733000}
>> hackyCore_Build.cruisecontrol        Failure         Ant
>> C:\HackystatSource\hackyCore_Build   04/10/2006-16:58:22
>> {projectName=Hackystat-All, runtime=1144724287789,
>> buildDate=1142866987000}
>>
>>
>> Note the "runtime" in pMap. From the data format in xml file on hard
>> disk, these pieces are sent using ant sensor after evolution. But the
>> weird thing is ant sensor uses "runTime" instead of "runtime".
>>
>> So, Julie, perhaps you need to update your sensor. In the mean time,
>> I'll put a try-catch block in my code.
>>
>> Cheers,
>>
>> Cedric
>>
>>
>> Philip Johnson wrote:
>>
>>>As further evidence, I just tried to run DailyProjectDetails on the public server for yesterday's Hackystat-7 data to see if it was returning in a reasonable amount of time.
>>>
>>>Well, the good news is, the DailyProjectDetails command now runs in less than a second.
>>>
>>>The bad news is that it returns a stack trace! :-)
>>>
>>>I assume that Cedric and Hongbing will work this out and deploy a new version to the public server today.
>>>
>>>Cheers,
>>>Philip
>>>
>>>
>>>----- Original Message -----
>>>From: "(Cedric) Qin ZHANG" <[EMAIL PROTECTED]>
>>>Date: Tuesday, April 11, 2006 3:26 am
>>>Subject: [HACKYSTAT-DEV-L] DailyProjectBuild cannot instaitiate.
>>>To: [email protected]
>>>
>>>
>>>
>>>>Hello,
>>>>
>>>>Who touched DailyProjecBuild recently? Any analysis depends on that
>>>>class throws exception.
>>>>
>>>>For example:
>>>>
>>>>org.hackystat.core.telemetry.reducer.TelemetryReducerException:
>>>>Error:
>>>>class org.hackystat.sdt.build.dailyproject.DailyProjectBuild could
>>>>not
>>>>be instantiated.
>>>>
>>>>Cedric
>>>>
>>>>
>>>>
>>
>

Reply via email to