Hi Hongbing,
This is an interesting problem. I have spent much of the day trying to
reproduce it by checking out the CVS modules in the state they were on
7-Oct just before the build. I have not found any conclusive failures,
but below is my thought process. I am still debugging this issue.
My initial thought (but unlikely) was that hackyTelemetry might have
been checked in to CVS with compilation errors, therefore causing the
LOCC parser to fail and no XML output produced. This turned out to be
false; the hackyTelemetry module was in tip-top shape and produced clean
data.
A little further digging revealed that not only hackyTelemetry was
affected, but no LOCC data was sent for the modules:
1) hackyTelemetry
2) hackyReportExample
3) hackyVisualStudio
4) hackyCli
5) hackyVim
6) hackyPerf
hackyEmacs and hackyBuild also did not have LOCC data, but this is to be
expected because they do not contain Java source files.
I am thinking that if this problem is related to LOCC, it is probably
not in the sensor, but in the LOCC application itself (e.g. the LOCC
tool produces XML output that the sensor can not read). However, I can
not understand why LOCC would process _some_ of the modules and not all.
I would expect uniform failure across all modules if the LOCC tool or
sensor was at fault.
Another issue added to the mix is the overlap of class files between
sensorshell.jar and sensor.locc.jar. When I released the new version of
LOCC on the night of 7-Oct (after the build), the sensorshell.jar file
on Xenia contained outdated class files for the LOCC sensor. This has
been a frequent problem, as the class files in sensorshell are used by
Ant before those in sensor.locc.jar.
Anyway, I am still actively working on this. I will give an update
later hopefully with the culprit identified and detained!
Thanks,
Mike
----- Original Message -----
From: Hongbing Kou <[EMAIL PROTECTED]>
Date: Friday, October 8, 2004 5:21 pm
Subject: Re: [HACKYSTAT-DEV-L:147] Preliminary result Re: Re: Hackystat
goes on diet: drops 10 KLOC in 24 hours!
> Hi, Mike,
>
> In configuration instance-ALL there is no data on hackyTelemetry
> sent out
> to server
> on day Oct 7, 2004. My suspicious is on locc sensor. Can you check
> the ANT LOCC
> sensor to see what's going on? I will do the same thing to see
> whether
> there is any
> bug too.
>
> Thanks,
> Hongbing
>
> At 11:38 AM 10/8/2004, Hongbing Kou wrote:
>
> >Hi,
> >
> >My preliminary is that the LOCC sensor works fine and sent data
> to public
> >server. I already
> >identified where the problem is from. Please look at the attached
> locc.xml
> >for details. Three
> >modules were missing in Oct 6 and one was added in Oct 7. I think
> there is
> >some work to
> >be done in DailyProjectFileMetric. I will work on it.
> >
> >Thanks,
> >Hongbing
> >
> >
> >At 10:24 AM 10/8/2004, (Cedric) Qin ZHANG wrote:
> >>Please go to "extra" page, choose "Telemetry Direct Streams"
> analysis,>>and input the following:
> >>
> >>streams SLOC = {FileMetric("SLOC")};
> >>streams SLOC = {WorkspaceFileMetric("SLOC")};
> >>
> >>
> >>There is no FileMetric data for hackyTelemetry on OCT 7. I don't
> know why
> >>this happened.
> >>
> >>Cheers,
> >>
> >>Cedric
> >>
> >>
> >>
> >>Philip Johnson wrote:
> >>>I'm getting Project Daily Summary reports, and the last two
> days show an
> >>>anomaly.
> >>>Here's the October 6 report:
> >>>
> >>>>hacky2004-all on 06-Oct-2004
> >>>> Active Time: 3.83 (total), 0 (yours)
> >>>> Build: 4 (total), 4 (successful).
> >>>> Churn: 898|162 (Total Added|Deleted), 235|0 (yours)
> >>>> Commits: 30 (Total|Distinct), 1 (yours)
> >>>> Coverage: 81.4% (Overall), 2574 (covered methods), 589
> (uncovered>>>> methods)
> >>>> File Metrics: 856 (classes), 3920 (methods), 56982 (LOC)
> >>>> Performance: 26 (total tests), 4 (failures)
> >>>> Review Active Time: (No data summary method available.)
> >>>> Review Issues: (No data summary method available.)
> >>>> Unit Tests: 532|5|1 (Total p|f|e),
> >>>
> >>>Note that the total size is around 56 KLOC.
> >>>Now look at last night's report:
> >>>
> >>>>hacky2004-all on 07-Oct-2004
> >>>> Active Time: 10.08 (total), 3.67 (yours)
> >>>> Build: 4 (total), 4 (successful).
> >>>> Churn: 1484|400 (Total Added|Deleted), 0|0 (yours)
> >>>> Commits: 78 (Total|Distinct), 0 (yours)
> >>>> Coverage: 81.3% (Overall), 2582 (covered methods), 592
> (uncovered>>>>methods)
> >>>> File Metrics: 754 (classes), 3409 (methods), 47934 (LOC)
> >>>> Performance: 26 (total tests), 2 (failures)
> >>>> Unit Tests: 612|10|2 (Total p|f|e), 11|0|1 (yours)
> >>>
> >>>The total size has dropped by almost 10K, even though the Churn
> data
> >>>indicates there should be a net increase of 1K to the code! It
> almost
> >>>looks like a module has been taken out of hackystat-ALL or
> something.>>>Does anyone have any insights into what's going on?
> >>>Cheers,
> >>>Philip
> >>>p.s. I continue to hack away on hackyReview. I've rewritten a
> lot of the
> >>>package as I've discovered what I think are some interesting
> design
> >>>patterns for the DailyProjectData level. I hope to commit in
> the next
> >>>few days.
> >
> >
> >
>
>
>
