Hi All,
I'm working on some code in hackyAnt. Apparently, I need hackyPerf to for the SensorDataType definition. I didn't know that at first, because everything compiled and all the unit test passed. But, I had the following error message on the console;
11/10 16:09:51 Error processing sensor.loadtest.xml
org.hackystat.kernel.sensor.SensorException: Sensor definition error: unknown sensordatatype:Perf
Again, everything compiled and tested ok. Which indicates a couple of problems:
1) the doInternal_hackyAnt target in the build.xml is wrong. I took a look at it and it says that hackyAnt depends on hackyTelemetry, which is obviously wrong. In addition, the README.html file said the same thing. It really should depend on hackyPerf. This isn't really a problem for the UH configuration because we build almost everything we have. So, the errors in the specific module dependencies go unnoticed. This will be confusing for people building their own configurations.
I propose an Ant target that prints out the module dependencies. That way we can double check them. I also think that this module dependency is something that should go into our DocBook documentation.
2) the other thing that confused me was the there are two modules; hackyPerf and hackyLoadTest (see the message below). I took a look at the two modules and it seems that hackyPerf contains the SDT and Performance Testing code. I assume hackyLoadTest is obsolete at this point, right?
A Side Note:
When should SensorDataTypes like Perf and Commit (which are not in hackyStdExt) go into hackyStdExt? Are we saying that FileMetric, Activity, etc are more standard SDT than Perf and Commit? Probably not... As you all know (and probably don't want to hear) is that we reached some threshold where the architectural design of Hackystat is causing problems... For example, the problem of where do the telemetry reducers go.
Another example of a problem is the following, hackyAnt requires hackyPerf; hackyPerf requires hackyTelemetry. So, hackyAnt requires hackyTelemetry without no obvious reason. I need to do all that so I can build hackyAnt. AH!!! junk.
thanks, aaron
At 12:29 PM 6/30/2004 -1000, you wrote:
Dear all,
As per Wednesday CSDL meeting discussion, two modules are renamed in our CVS repository.
(1) hackyPerf is renamed to hackyLoadTest.
If you have hackyPerf in you local disk, please delete it and check out hackyLoadTest. If you have unchecked-in code (which is highly unlikely), please contact me to resolve the issue.
I will import a new module which is called hackyPerf, but this one will be completely independent of the _old_ hackyPerf.
